Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding examples created for previous demo #287

Merged
merged 9 commits into from
Sep 19, 2017
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
###
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file seems kind of pointless to me, it lists creating a SP based on a template and powering it on, but that is already illustrated in the basic oneview_server_profile.yml example: link

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes, but it was part of the requested scenarios, I renamed to step 3 and use it again in step 4, so the user can compare tasks.

# Copyright 2017 Hewlett Packard Enterprise Development LP
#
# Licensed under the Apache License, Version 2.0 (the "License");
# You may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
###

- hosts: all
vars:
config: '{{ playbook_dir }}/oneview_config.json'
server_hardware_name: "2-USE722C99W-M, bay 12"
server_profile_template: "Windows2016_i3s"
profile_name: "profile_i3s"

tasks:

- name : "Create Server Profile - {{ profile_name }}"
oneview_server_profile:
config: "{{ config }}"
data:
server_hardware: "{{ server_hardware_name }}"
Copy link
Contributor

@fgbulsoni fgbulsoni Sep 11, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not work anymore as server_hardware was not following the style guide from other fields. It should be serverHardwareName now.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

server_template: "{{ server_profile_template }}"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not work anymore as server_template was not following the style guide from other fields. It should be serverProfileTemplateName now.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

name: "{{ profile_name }}"
delegate_to: localhost

- name: Power on the server hardware
oneview_server_hardware:
config: "{{ config }}"
state: power_state_set
data:
name : "{{ server_hardware.name }}"
powerStateData:
powerState: "On"
powerControl: "MomentaryPress"
delegate_to: localhost
114 changes: 114 additions & 0 deletions examples/based_on_server_profile_boot_from_SAN_add_another_volume.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,114 @@
###
# Copyright 2017 Hewlett Packard Enterprise Development LP
#
# Licensed under the Apache License, Version 2.0 (the "License");
# You may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
###

- hosts: all
vars:
config: '{{ playbook_dir }}/oneview_config.json'
server_hardware_type_name: "SY 480 Gen9 3"
enclosure_group_name: "SYN107_EG"
server_hardware_name: "2-USE722C99W-M, bay 1"
profile_name: "profile_san"
management_network: "Management"
SAN_A_network: "SAN-A"
SAN_B_network: "SAN-B"
storage_pool_name_A: "Pool name A"
storage_pool_name_B: "Pool name B"

tasks:

- name : "Create/Update Server Profile - {{ profile_name }}"
oneview_server_profile:
config: "{{ config }}"
data:
name: "{{ profile_name }}"
serverHardwareTypeName: "{{ server_hardware_type_name }}"
enclosureGroupName: "{{ enclosure_group_name }}"
server_hardware: "{{ server_hardware_name }}"
Copy link
Contributor

@fgbulsoni fgbulsoni Sep 11, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not work anymore as server_hardware was not following the style guide from other fields. It should be serverHardwareName now.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

serialNumberType: Virtual
iscsiInitiatorNameType: AutoGenerated
macType: Virtual
wwnType: Virtual
description: 'use case 1: boot from SAN'
affinity: Bay
connections:
- id: 1
name: LAB
functionType: Ethernet
portId: Mezz 3:2-a
requestedMbps: '2500'
networkName: "{{ management_network }}"
requestedVFs: '0'
boot:
priority: NotBootable
- id: 2
name: SAN-A
functionType: FibreChannel
portId: Mezz 2:1
requestedMbps: Auto
networkName: "{{ SAN_A_network }}"
boot:
priority: Primary
bootVolumeSource: ManagedVolume
- id: 3
name: SAN-B
functionType: FibreChannel
portId: Mezz 2:2
requestedMbps: Auto
networkName: "{{ SAN_B_network }}"
boot:
priority: NotBootable
boot:
manageBoot: true
order:
- CD
- USB
- HardDisk
- PXE
bootMode:
manageMode: true
mode: BIOS
bios:
manageBios: false
overriddenSettings: []
hideUnusedFlexNics: true
iscsiInitiatorName: ''
localStorage:
sasLogicalJBODs: []
controllers: []
sanStorage:
hostOSType: Windows Server 2016
manageSanStorage: true
volumeAttachments:
- id: 1
isBootVolume: true
lunType: Auto
storagePaths:
- isEnabled: true
connectionId: 2
- isEnabled: true
connectionId: 3
volumeName: win_boot
volumeStoragePoolName: "{{ storage_pool_name_A }}"
- id: 2
lunType: Auto
storagePaths:
- isEnabled: true
connectionId: 2
- isEnabled: true
connectionId: 3
volumeName: DATA1
volumeStoragePoolName: "{{ storage_pool_name_B }}"
delegate_to: localhost
115 changes: 115 additions & 0 deletions examples/create_server_profile_boot_from_SAN.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,115 @@
###
# Copyright 2017 Hewlett Packard Enterprise Development LP
#
# Licensed under the Apache License, Version 2.0 (the "License");
# You may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
###

- hosts: all
vars:
config: '{{ playbook_dir }}/oneview_config.json'
server_hardware_type_name: "SY 480 Gen9 3"
enclosure_group_name: "SYN107_EG"
server_hardware_name: "2-USE722C99W-M, bay 1"
profile_name: "profile_san"
management_network: "Management"
SAN_A_network: "SAN-A"
SAN_B_network: "SAN-B"
storage_pool_name_A: "Pool name A"

tasks:

- name : "Create Server Profile - {{ profile_name }}"
oneview_server_profile:
config: "{{ config }}"
data:
name: "{{ profile_name }}"
serverHardwareTypeName: "{{ server_hardware_type_name }}"
enclosureGroupName: "{{ enclosure_group_name }}"
server_hardware: "{{ server_hardware_name }}"
Copy link
Contributor

@fgbulsoni fgbulsoni Sep 11, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This will not work anymore as server_hardware was not following the style guide from other fields. It should be serverHardwareName now.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

serialNumberType: Virtual
iscsiInitiatorNameType: AutoGenerated
macType: Virtual
wwnType: Virtual
description: 'use case 1: boot from SAN'
affinity: Bay
connections:
- id: 1
name: LAB
functionType: Ethernet
portId: Mezz 3:2-a
requestedMbps: '2500'
networkName: "{{ management_network }}"
requestedVFs: '0'
boot:
priority: NotBootable
- id: 2
name: SAN-A
functionType: FibreChannel
portId: Mezz 2:1
requestedMbps: Auto
networkName: "{{ SAN_A_network }}"
boot:
priority: Primary
bootVolumeSource: ManagedVolume
- id: 3
name: SAN-B
functionType: FibreChannel
portId: Mezz 2:2
requestedMbps: Auto
networkName: "{{ SAN_B_network }}"
boot:
priority: NotBootable
boot:
manageBoot: true
order:
- CD
- USB
- HardDisk
- PXE
bootMode:
manageMode: true
mode: BIOS
bios:
manageBios: false
overriddenSettings: []
hideUnusedFlexNics: true
iscsiInitiatorName: ''
localStorage:
sasLogicalJBODs: []
controllers: []
sanStorage:
hostOSType: Windows Server 2016
manageSanStorage: true
volumeAttachments:
- id: 1
isBootVolume: true
lunType: Auto
storagePaths:
- isEnabled: true
connectionId: 2
- isEnabled: true
connectionId: 3
volumeName: win_boot
volumeStoragePoolName: "{{ storage_pool_name_A }}"
delegate_to: localhost

- name: Power on the server hardware
oneview_server_hardware:
config: "{{ config }}"
state: power_state_set
data:
name : "{{ server_hardware.name }}"
powerStateData:
powerState: "On"
powerControl: "MomentaryPress"
delegate_to: localhost
Loading