Fwd: Understanding yaml field
Jorge O. Castro
jorge at ubuntu.com
Wed Dec 9 17:54:29 UTC 2015
Hi folks, is anyone available to give Anand a hand?
---------- Forwarded message ----------
From: Anand S K <A.Shivamogga.Krishn at hgst.com>
Date: Thu, Dec 3, 2015 at 8:03 AM
Subject: RE: Understanding yaml field
To: "Jorge O. Castro" <jorge at ubuntu.com>
Hi Jorge,
Thanks for the reply. I have a fair understanding of the yaml
structure now.
I have a setup with one maas server and 3 nodes. Openstack deploys
successfully when I deploy the base openstack
juju quickstart openstack-base/36
On the same setup I tried to deploy the openstack using juju-deployer
Juju-deployer -d -c default.yaml openstack-liberty-git
Openstack was getting deployed to VMs that were not in my setup. Then
I tried to deploy simple services(attached with mail), I get following
messages
root at MAAS:/# juju-deployer -d -c WIP_1.yaml openstack-liberty-git
2015-12-03 03:37:40 [DEBUG] deployer.cli: Using runtime GoEnvironment on maas
2015-12-03 03:37:40 [INFO] deployer.cli: Starting deployment of
openstack-liberty-git
2015-12-03 03:37:41 [DEBUG] deployer.env: Connected to environment
2015-12-03 03:37:41 [DEBUG] deployer.import: Getting charms...
2015-12-03 03:37:43 [DEBUG] deployer.deploy: Resolving configuration
2015-12-03 03:37:43 [INFO] deployer.import: Deploying services...
2015-12-03 03:37:43 [DEBUG] deployer.import:
<deployer.env.go.GoEnvironment object at 0x7f86d9cc2b90>
2015-12-03 03:37:44 [INFO] deployer.import: Deploying service
nova-compute using local:precise/nova-compute
2015-12-03 03:37:58 [DEBUG] deployer.import: Adding units...
2015-12-03 03:37:58 [DEBUG] deployer.import: Service 'nova-compute'
does not need any more units added.
2015-12-03 03:37:58 [DEBUG] deployer.import: Waiting for units before
adding relations
2015-12-03 03:38:05 [DEBUG] deployer.env: Delta machine: 1 change:error
2015-12-03 03:38:15 [DEBUG] deployer.env: Delta machine: 2 change:error
2015-12-03 03:38:30 [DEBUG] deployer.env: Delta machine: 3 change:error
2015-12-03 04:12:30 [DEBUG] deployer.env: Delta relation:
[openstack-dashboard:cluster:peer] change:created
2015-12-03 04:12:30 [DEBUG] deployer.env: Delta service:
openstack-dashboard change:{u'Err': None, u'Since':
u'2015-12-03T12:12:34.675787661Z', u'Current': u'unknown', u'Version':
u'', u'Message': u'Waiting for agent initialization to finish',
u'Data': {}}
2015-12-03 04:12:30 [DEBUG] deployer.env: Delta unit:
openstack-dashboard/0 change:pending
2015-12-03 04:12:30 [DEBUG] deployer.env: Delta machine: 4 change:pending
2015-12-03 04:12:45 [DEBUG] deployer.env: Delta machine: 4 change:error
2015-12-03 04:57:27 [INFO] deployer.import: Adding relations...
2015-12-03 04:57:28 [INFO] deployer.cli: Deployment complete in 4787.86 seconds
root at MAAS:/# juju-deployer -d -c WIP_dashboard.yaml -d openstack-liberty-git
2015-12-03 04:12:21 [DEBUG] deployer.cli: Using runtime GoEnvironment on maas
2015-12-03 04:12:21 [INFO] deployer.cli: Starting deployment of
openstack-liberty-git
2015-12-03 04:12:22 [DEBUG] deployer.env: Connected to environment
2015-12-03 04:12:22 [DEBUG] deployer.import: Getting charms...
2015-12-03 04:12:24 [DEBUG] deployer.deploy: Resolving configuration
2015-12-03 04:12:24 [INFO] deployer.import: Deploying services...
2015-12-03 04:12:24 [DEBUG] deployer.import:
<deployer.env.go.GoEnvironment object at 0x7f4d72c28b90>
2015-12-03 04:12:25 [INFO] deployer.import: Deploying service
openstack-dashboard using local:precise/openstack-dashboard
2015-12-03 04:12:35 [DEBUG] deployer.import: Adding units...
2015-12-03 04:12:36 [DEBUG] deployer.import: Service
'openstack-dashboard' does not need any more units added.
2015-12-03 04:12:36 [DEBUG] deployer.import: Waiting for units before
adding relations
2015-12-03 04:12:45 [DEBUG] deployer.env: Delta machine: 4 change:error
2015-12-03 04:57:30 [INFO] deployer.import: Adding relations...
2015-12-03 04:57:31 [INFO] deployer.cli: Deployment complete in 2709.95 seconds
root at MAAS:/# juju status
environment: maas
machines:
"0":
agent-state: started
agent-version: 1.25.0
dns-name: heartfelt-bat.maas
instance-id: /MAAS/api/1.0/nodes/node-46ed2392-8ddd-11e5-b890-000c298c60eb/
series: trusty
hardware: arch=amd64 cpu-cores=16 mem=10240M
state-server-member-status: has-vote
"1":
agent-state: error
agent-state-info: 'gomaasapi: got error back from server: 400 BAD
REQUEST ({"distro_series":
["''precise'' is not a valid distro_series. It should be one
of: '''', ''ubuntu/trusty''."]})'
instance-id: pending
series: precise
"2":
agent-state: error
agent-state-info: 'gomaasapi: got error back from server: 400 BAD
REQUEST ({"distro_series":
["''precise'' is not a valid distro_series. It should be one
of: '''', ''ubuntu/trusty''."]})'
instance-id: pending
series: precise
"3":
agent-state: error
agent-state-info: 'gomaasapi: got error back from server: 400 BAD
REQUEST ({"distro_series":
["''precise'' is not a valid distro_series. It should be one
of: '''', ''ubuntu/trusty''."]})'
instance-id: pending
series: precise
"4":
agent-state: error
agent-state-info: 'cannot run instances: cannot run instances:
gomaasapi: got
error back from server: 409 CONFLICT (No available node matches
constraints:
mem=1024.0 zone=default)'
instance-id: pending
series: precise
services:
nova-compute:
charm: local:precise/nova-compute-133
exposed: false
service-status:
current: unknown
message: Waiting for agent initialization to finish
since: 03 Dec 2015 03:37:53-08:00
relations:
compute-peer:
- nova-compute
units:
nova-compute/0:
workload-status:
current: unknown
message: Waiting for agent initialization to finish
since: 03 Dec 2015 03:37:53-08:00
agent-status:
current: allocating
since: 03 Dec 2015 03:37:53-08:00
agent-state: pending
machine: "1"
nova-compute/1:
workload-status:
current: unknown
message: Waiting for agent initialization to finish
since: 03 Dec 2015 03:37:55-08:00
agent-status:
current: allocating
since: 03 Dec 2015 03:37:55-08:00
agent-state: pending
machine: "2"
nova-compute/2:
workload-status:
current: unknown
message: Waiting for agent initialization to finish
since: 03 Dec 2015 03:37:57-08:00
agent-status:
current: allocating
since: 03 Dec 2015 03:37:57-08:00
agent-state: pending
machine: "3"
openstack-dashboard:
charm: local:precise/openstack-dashboard-32
exposed: false
service-status:
current: unknown
message: Waiting for agent initialization to finish
since: 03 Dec 2015 04:12:34-08:00
relations:
cluster:
- openstack-dashboard
units:
openstack-dashboard/0:
workload-status:
current: unknown
message: Waiting for agent initialization to finish
since: 03 Dec 2015 04:12:34-08:00
agent-status:
current: allocating
since: 03 Dec 2015 04:12:34-08:00
agent-state: pending
machine: "4"
root at MAAS:/#
-----Original Message-----
From: jorge.castro at gmail.com [mailto:jorge.castro at gmail.com] On Behalf
Of Jorge O. Castro
Sent: Saturday, November 28, 2015 8:02 AM
To: Anand S K <A.Shivamogga.Krishn at hgst.com>
Subject: Re: Understanding yaml field
Hello!
I saw your question here:
http://askubuntu.com/questions/702874/openstack-juju-yaml-field-explanations/703398#703398
And I've done my best to answer it, I will have more engineers review
the answer and add more detail if you'd like, thanks!
On Fri, Nov 27, 2015 at 12:29 PM, Anand S K
<A.Shivamogga.Krishn at hgst.com> wrote:
> Hi Jorge,
>
>
>
> I am engineer with HGST. I have successfully deployed Openstack using
> Juju charms in a local setup. I am trying to deploy openstack using yaml file.
>
>
>
> Can you explain the meaning of the following key-value pairs in the
> following text and how juju interprets and works on these values?(or
> share the link that explains this. I went through the link
> http://pythonhosted.org/juju-deployer/config.html#placement but still
> have difficulty in understanding it). It is part of the yaml bundle
> for deploying openstack.
>
> keystone:
>
> annotations:
>
> gui-x: '500'
>
> gui-y: '0'
>
> charm: cs:trusty/keystone-31
>
> num_units: 1
>
> options:
>
> admin-password: openstack
>
> ha-mcastport: 5403
>
> openstack-origin: cloud:trusty-liberty
>
> to:
>
> - lxc:3
>
>
>
>
>
> Regards
>
> Anand
>
> HGST E-mail Confidentiality Notice & Disclaimer:
> This e-mail and any files transmitted with it may contain confidential
> or legally privileged information of HGST and are intended solely for
> the use of the individual or entity to which they are addressed. If
> you are not the intended recipient, any disclosure, copying,
> distribution or any action taken or omitted to be taken in reliance on
> it, is prohibited. If you have received this e-mail in error, please
> notify the sender immediately and delete the e-mail in its entirety from your system.
--
Jorge Castro
Canonical Ltd.
http://jujucharms.com/ - The fastest way to model your service
HGST E-mail Confidentiality Notice & Disclaimer:
This e-mail and any files transmitted with it may contain confidential
or legally privileged information of HGST and are intended solely for
the use of the individual or entity to which they are addressed. If
you are not the intended recipient, any disclosure, copying,
distribution or any action taken or omitted to be taken in reliance on
it, is prohibited. If you have received this e-mail in error, please
notify the sender immediately and delete the e-mail in its entirety
from your system.
--
Jorge Castro
Canonical Ltd.
http://jujucharms.com/ - The fastest way to model your service
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dashboard.yaml
Type: application/octet-stream
Size: 467 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/juju/attachments/20151209/fa8e8f9e/attachment.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nova.yaml
Type: application/octet-stream
Size: 534 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/juju/attachments/20151209/fa8e8f9e/attachment-0001.obj>
More information about the Juju
mailing list