omgjlk

2016-06-14 20:16:39,162 p=4922 u=blueboxadmin |  RUNNING HANDLER [common : meta] ************************************************
2016-06-14 20:16:39,362 p=4922 u=blueboxadmin |  fatal: [ds0005.tor01-lab]: FAILED! => {"failed": true, "msg": "The module meta was not found in configured module paths. Additionally, core modules are missing. If this is a checkout, run 'git submodule update --init --recursive' to correct this problem."}

omgjlk

2016-06-09 18:02:21.667 19955 ERROR nova.compute.manager [instance: c719812c-2776-4ff9-984d-03dcf1396b4d] Traceback (most recent call last):
2016-06-09 18:02:21.667 19955 ERROR nova.compute.manager [instance: c719812c-2776-4ff9-984d-03dcf1396b4d]   File "/opt/bbc/openstack-2016.1-mitaka/nova/local/lib/python2.7/site-packages/nova/compute/manager.py", line 4736, in _attach_volume
2016-06-09 18:02:21.667 19955 ERROR nova.compute.manager [instance: c719812c-2776-4ff9-984d-03dcf1396b4d]     do_check_attach=False, do_driver_attach=True)
2016-06-09 18:02:21.667 19955 ERROR nova.compute.manager [instance: c719812c-2776-4ff9-984d-03dcf1396b4d]   File "/opt/bbc/openstack-2016.1-mitaka/nova/local/lib/python2.7/site-packages/nova/virt/block_device.py", line 54, in wrapped
2016-06-09 18:02:21.667 19955 ERROR nova.compute.manager [instance: c719812c-2776-4ff9-984d-03dcf1396b4d]     ret_val = method(obj, context, *args, **kwargs)
2016-06-09 18:02:21.667 19955 ERROR nova.compute.manager [instance: c719812c-2776-4ff9-984d-03

omgjlk

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: 'list' object has no attribute 'startswith'
fatal: [10.230.7.178]: FAILED! => {"changed": false, "failed": true, "module_stderr": 
"Traceback (most recent call last):\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", 
line 302, in <module>\n    main()\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", 
line 274, in main\n    if rabbitmq_user.get():\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", 
line 155, in get\n    users = self._exec(['list_users'], True)\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", 
line 150, in _exec\n    rc, out, err = self.module.run_command(cmd + args, check_rc=True)\n  
File \"/tmp/ansible_MRA1FL/ansible_modlib.zip/ansible/module_utils/basic.py\", line 1993, in run_command\n  
File \"/usr/lib/python2.7/posixpath.py\", line 261, in expanduser\n    
if not path.startswith('~'):\nAttributeError: 'list' object h

omgjlk

An exception occurred during task execution. To see the full traceback, use -vvv. The error was: AttributeError: 'list' object has no attribute 'startswith'
fatal: [10.230.7.178]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", line 302, in <module>\n    main()\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", line 274, in main\n    if rabbitmq_user.get():\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", line 155, in get\n    users = self._exec(['list_users'], True)\n  File \"/tmp/ansible_MRA1FL/ansible_module_rabbitmq_user.py\", line 150, in _exec\n    rc, out, err = self.module.run_command(cmd + args, check_rc=True)\n  File \"/tmp/ansible_MRA1FL/ansible_modlib.zip/ansible/module_utils/basic.py\", line 1993, in run_command\n  File \"/usr/lib/python2.7/posixpath.py\", line 261, in expanduser\n    if not path.startswith('~'):\nAttributeError: 'list' object has no at

omgjlk

kilpkg-controller-0:~$ dig @8.8.8.8 www.nps.org

; <<>> DiG 9.9.5-3ubuntu0.8-Ubuntu <<>> @8.8.8.8 www.nps.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22604
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:

omgjlk

TASK [setup] *******************************************************************
<169.45.113.43> ESTABLISH SSH CONNECTION FOR USER: ubuntu
<169.45.113.43> SSH: ansible.cfg set ssh_args: (-o)(LogLevel=quiet)(-o)(StrictHostKeyChecking=no)(-o)(UserKnownHostsFile=/dev/null)(-i)(/Users/jkeating/src/ursula.old/test/../envs/test/int-test.pem)(-o)(ControlMaster=auto)(-o)(ControlPath=~/.ssh/controlmasters/u-%r@%h:%p)(-o)(ControlPersist=300)
<169.45.113.43> SSH: ANSIBLE_HOST_KEY_CHECKING/host_key_checking disabled: (-o)(StrictHostKeyChecking=no)
<169.45.113.43> SSH: ansible_password/ansible_ssh_pass not set: (-o)(KbdInteractiveAuthentication=no)(-o)(PreferredAuthentications=gssapi-with-mic,gssapi-keyex,hostbased,publickey)(-o)(PasswordAuthentication=no)
<169.45.113.43> SSH: ANSIBLE_REMOTE_USER/remote_user/ansible_user/user/-u set: (-o)(User=ubuntu)
<169.45.113.43> SSH: ANSIBLE_TIMEOUT/timeout set: (-o)(ConnectTimeout=10)
<169.45.113.43> SSH: PlayContext set ssh_common_args: ()
<169.45.113.43> SSH: PlayContext set ssh_e

omgjlk

#
# This playbook will automatically accept host keys into the known_hosts
# file for every host in the inventory. Takes an extra argument to define the
# ssh config file to use (relative to playbook location):
#   -e ssh_config=../../openstack-envs/zelda-tor/ssh_config
#
---
- name: Load Keys
  hosts: localhost
  connection: local

omgjlk

  subnets:
    - name: internal_v4
      network_name: internal
      ip_version: 4
      cidr: 172.16.255.0/24
      pool_start: 172.16.255.2
      pool_end: 172.16.255.254
      enable_dhcp: "true"
      gateway_ip: 172.16.255.1
      dns_nameservers: '8.8.8.8,8.8.4.4'

omgjlk

- name: update-alternatives
  alternatives: name={{ item }}
                path={{ openstack_package.virtualenv_base }}/{{ project_name }}/bin/{{ item }}
                link=/usr/local/bin/{{ item }}
  with_items: "{{ alternatives }}"
  when: alternatives is defined
  
  
  results in 
  

omgjlk

multi-region cloud​
customer can address cloud resources across multiple regions. customer has a single set of api endpoint and management interface used to manage cloud resources across all regions.the_cloud
--------------
     |-- hong kong region
     |-- london region
     |-- seattle regionDashboard
1a. User logs into Horizon Dashboard
2a. User sees resources presented in subsets (regions)
3a. User can manage and deploy resources across different regionsCLI/API
1b. User authenticates via CLI/API