Re: 答复: 答复: Using maas+juju to deploy openstack,I can't run 02-maasdeploy.sh successfully.

2015-12-08 Thread Narinder Gupta 
in the file below entry defines it
# Defines the general setup for the MAAS environment, including the

# username and password for the host as well as the MAAS server.

user: ubuntu

password: ubuntu

But you need to redeploy to test.

Thanks and Regards,
Narinder Gupta (PMP)   narinder.gu...@canonical.com
Canonical, Ltd.narindergupta [irc.freenode.net]
+1.281.736.5150narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com


On Tue, Dec 8, 2015 at 8:16 PM, zhangyuanyou <zhangyuan...@huawei.com>
wrote:

> Hi Narinder Gupta,
>
>  Now  I am use the user onos ,password root,
>
>  Where should I modify in the file deployments.yaml?
>
> Could you show me?
>
>
>
> Thanks and Regards,
>
> yuanyou
>
>
>
> *发件人:* zhangyuanyou
> *发送时间:* 2015年12月7日 9:48
> *收件人:* 'Narinder Gupta'
> *抄送:* artur.tyl...@canonical.com; billy.ol...@canonical.com;
> Weidong.Shao; juju@lists.ubuntu.com
> *主题:* 答复: 答复: Using maas+juju to deploy openstack,I can't run
> 02-maasdeploy.sh successfully.
>
>
>
> Hi Narinder Gupta,
>
> I can login maas server by ssh onos@192.168.212.140 successfully.
>
> I had uploaded the file ,please check it.
>
> Thanks for your help!
>
>
>
> Yuanyou
>
>
>
> *发件人:* Narinder Gupta [mailto:narinder.gu...@canonical.com
> <narinder.gu...@canonical.com>]
> *发送时间:* 2015年12月5日 23:20
> *收件人:* zhangyuanyou
> *抄送:* artur.tyl...@canonical.com; billy.ol...@canonical.com;
> Weidong.Shao; juju@lists.ubuntu.com
> *主题:* Re: 答复: Using maas+juju to deploy openstack,I can't run
> 02-maasdeploy.sh successfully.
>
>
>
> Yuanyou,
>
> Will you please send me following details?
>
>
>
> deployments.yaml file also script 02-maasdeployment.sh
>
>
>
> Also try the following:
>
>
>
> try to ssh into the maas server and see whether it works or not? ssh 
> *onos@192.168.212.140
> <onos@192.168.212.140>**  also whether you are able to ping or not to
> 192.168.212.140.*
>
>
>
> *Also please send me your jump host config details. specially
> /etc/network/interfaces file.i*
>
>
> Thanks and Regards,
>
> Narinder Gupta (PMP)   narinder.gu...@canonical.com
>
> Canonical, Ltd.narindergupta [irc.freenode.net]
>
> +1.281.736.5150narindergupta2007[skype]
>
>
>
> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
>
>
>
> On Sat, Dec 5, 2015 at 2:50 AM, zhangyuanyou <zhangyuan...@huawei.com>
> wrote:
>
> Hi Narinder Gupta,
>
> I had to change to user onos,but it doesn’t work. Is it shoulb be user
> ubuntu?
>
> My host environment is like this:
>
>Maas server :
>
> Ip:192.168.212.140
>
> user :root
>
> password:root
>
>
>
> user:onos
>
> password:root
>
>Thanks,
>
> Yuanyou
>
>
>
> *发件人:* Narinder Gupta [mailto:narinder.gu...@canonical.com]
> *发送时间:* 2015年12月5日 14:50
> *收件人:* zhangyuanyou
> *抄送:* artur.tyl...@canonical.com; billy.ol...@canonical.com;
> Weidong.Shao; juju@lists.ubuntu.com
> *主题:* Re: Using maas+juju to deploy openstack,I can't run
> 02-maasdeploy.sh successfully.
>
>
>
> For more information about ATT recent setup please follow this link which
> works well https://wiki.opnfv.org/copper/academy/joid
>
>
>
>
>
>
> Thanks and Regards,
>
> Narinder Gupta (PMP)   narinder.gu...@canonical.com
>
> Canonical, Ltd.narindergupta [irc.freenode.net]
>
> +1.281.736.5150narindergupta2007[skype]
>
>
>
> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
>
>
>
> On Sat, Dec 5, 2015 at 12:34 AM, Narinder Gupta <
> narinder.gu...@canonical.com> wrote:
>
> Hi Yuanyou,
>
> Will you please let me know your host environment and I am wondering you
> are using root user? I have not tested 02-maasdeploy.sh script with root
> user yet. Will you please try it with ubuntu user?
>
>
>
> Will you please try this with latest git repository as i checked in few
> changes recently within couple of days for JOID.
>
>
>
> In new version i have added default lab which is very much like you
> are trying the MAAS on.  I tried to configure the ssh appropriately in
> script before i copy the values. So may be running as ubuntu user should be
> good. Also in yaml file try the ubuntu user.
>
>
>
> Same was tested by 4 different labs so far it is working.
>
>
>
>
> Thanks and Regards,
>
> Narinder Gupta (PMP

答复: Using maas+juju to deploy openstack,I can't run 02-maasdeploy.sh successfully.

2015-12-05 Thread zhangyuanyou 
b/python2.7/subprocess.py", line 1455, in _communicate_with_poll
ready = poller.poll()


Thanks
yuanyou

发件人: Billy Olsen [mailto:billy.ol...@canonical.com]
发送时间: 2015年12月5日 13:16
收件人: zhangyuanyou
抄送: artur.tyl...@canonical.com; Weidong.Shao; juju@lists.ubuntu.com
主题: Re: Using maas+juju to deploy openstack,I can't run 02-maasdeploy.sh 
successfully.

So what this seems to be indicating is either a) the ssh key isn't properly 
setup as part of the MAAS cloud unit script, b) the private key doesn't match 
the public key installed, c) something else I can't think of at the moment.

Can we get the full maas-deployer logs? That may shed some light on what's 
going on.

Artur, perhaps something else comes to mind? It's almost as if it's not fully 
cleaned up...

Billy

 The maas-deployer should be creating/using the ssh key that's available in 
/root/.ssh/id_maas according to the logs, because it's running as root. I don't 
currently have access to the script for this (02-maasdeploy.sh) so I'm not 100% 
sure of the context you are running this.

If you don't have another maas environment setup on the same host, something 
you can try is to remove the /root/.ssh/id_maas* keys

On Friday, December 4, 2015, zhangyuanyou 
<zhangyuan...@huawei.com<mailto:zhangyuan...@huawei.com>> wrote:
Hi  Artur Tyloch,
   I'm working on maas+juju to deploy openstack,now I edit the 02-maasdeploy.sh 
and excute it.
But this line "maas-deployer -c deployment.yaml -d --force" can't pass ,it 
always let me to input the password like this:

2015-12-04 17:45:54,032 DEBUG Executing: 'virt-install --connect qemu:///system 
--name opnfv-maas-intel --ram 4096 --vcpus 4 --disk 
vol=default/opnfv-maas-intel-root.img,format=qcow2,bus=virtio,io=native --disk 
vol=default/opnfv-maas-intel-seed.img,format=raw,bus=virtio,io=native --network 
bridge=brAdm,model=virtio --network bridge=brData,model=virtio --network 
bridge=brPublic,model=virtio --noautoconsole --vnc --import' stdin=''
2015-12-04 17:45:55,145 DEBUG Executing: 'virsh -c qemu:///system autostart 
opnfv-maas-intel' stdin=''
2015-12-04 17:45:55,162 DEBUG Waiting for MAAS vm to come up for ssh..
2015-12-04 17:45:55,163 DEBUG Using ip address specified: 192.168.212.140
2015-12-04 17:45:55,163 DEBUG Executing: 'ssh -i /root/.ssh/id_maas -o 
UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no 
root@192.168.212.140<javascript:_e(%7B%7D,'cvml','root@192.168.212.140');> 
true' stdin=''
root@192.168.212.140's<javascript:_e(%7B%7D,'cvml','root@192.168.212.140%5Cx27s');>
 password:

I edited the file deployment.yaml like this:
demo-maas:
maas:
# Defines the general setup for the MAAS environment, including the
# username and password for the host as well as the MAAS server.
user: root
password: root

# Contains the virtual machine parameters for creating the MAAS virtual
# server. Here you can configure the name of the virsh domain, the
# parameters for how the network is attached.
name: opnfv-maas-intel
interfaces: 
['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']
memory: 4096
vcpus: 4
arch: amd64
pool: default
disk_size: 160G

# Apt http proxy setting(s)
apt_http_proxy:

apt_sources:
  - ppa:maas/stable
  - ppa:juju/stable

# Virsh power settings
# Specifies the uri and keys to use for virsh power control of the
# juju virtual machine. If the uri is omitted, the value for the
# --remote is used. If no power settings are desired, then do not
# supply the virsh block.
virsh:
rsa_priv_key: /home/ubuntu/.ssh/id_rsa
rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub
#uri: 
qemu+ssh://ubuntu@10.4.1.1/system<http://ubuntu@10.4.1.1/system>

# Defines the IP Address that the configuration script will use to
# to access the MAAS controller via SSH.
ip_address: 192.168.212.140

Could you help me to resolve the question ? Any assistance is greatly 
appreciated.
Thanks.
Yuanyou




--
Billy Olsen
billy.ol...@canonical.com<mailto:billy.ol...@canonical.com>
Software Engineer
Canonical USA

-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Using maas+juju to deploy openstack,I can't run 02-maasdeploy.sh successfully.

2015-12-04 Thread zhangyuanyou 
Hi  Artur Tyloch,
   I'm working on maas+juju to deploy openstack,now I edit the 02-maasdeploy.sh 
and excute it.
But this line "maas-deployer -c deployment.yaml -d --force" can't pass ,it 
always let me to input the password like this:

2015-12-04 17:45:54,032 DEBUG Executing: 'virt-install --connect qemu:///system 
--name opnfv-maas-intel --ram 4096 --vcpus 4 --disk 
vol=default/opnfv-maas-intel-root.img,format=qcow2,bus=virtio,io=native --disk 
vol=default/opnfv-maas-intel-seed.img,format=raw,bus=virtio,io=native --network 
bridge=brAdm,model=virtio --network bridge=brData,model=virtio --network 
bridge=brPublic,model=virtio --noautoconsole --vnc --import' stdin=''
2015-12-04 17:45:55,145 DEBUG Executing: 'virsh -c qemu:///system autostart 
opnfv-maas-intel' stdin=''
2015-12-04 17:45:55,162 DEBUG Waiting for MAAS vm to come up for ssh..
2015-12-04 17:45:55,163 DEBUG Using ip address specified: 192.168.212.140
2015-12-04 17:45:55,163 DEBUG Executing: 'ssh -i /root/.ssh/id_maas -o 
UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no 
root@192.168.212.140 true' stdin=''
root@192.168.212.140's password:

I edited the file deployment.yaml like this:
demo-maas:
maas:
# Defines the general setup for the MAAS environment, including the
# username and password for the host as well as the MAAS server.
user: root
password: root

# Contains the virtual machine parameters for creating the MAAS virtual
# server. Here you can configure the name of the virsh domain, the
# parameters for how the network is attached.
name: opnfv-maas-intel
interfaces: 
['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']
memory: 4096
vcpus: 4
arch: amd64
pool: default
disk_size: 160G

# Apt http proxy setting(s)
apt_http_proxy:

apt_sources:
  - ppa:maas/stable
  - ppa:juju/stable

# Virsh power settings
# Specifies the uri and keys to use for virsh power control of the
# juju virtual machine. If the uri is omitted, the value for the
# --remote is used. If no power settings are desired, then do not
# supply the virsh block.
virsh:
rsa_priv_key: /home/ubuntu/.ssh/id_rsa
rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub
#uri: qemu+ssh://ubuntu@10.4.1.1/system

# Defines the IP Address that the configuration script will use to
# to access the MAAS controller via SSH.
ip_address: 192.168.212.140

Could you help me to resolve the question ? Any assistance is greatly 
appreciated.

Thanks.
Yuanyou


-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Using maas+juju to deploy openstack, I can't run 02-maasdeploy.sh successfully.

2015-12-04 Thread Narinder Gupta 
Hi Yuanyou,
Will you please let me know your host environment and I am wondering you
are using root user? I have not tested 02-maasdeploy.sh script with root
user yet. Will you please try it with ubuntu user?

Will you please try this with latest git repository as i checked in few
changes recently within couple of days for JOID.

In new version i have added default lab which is very much like you
are trying the MAAS on.  I tried to configure the ssh appropriately in
script before i copy the values. So may be running as ubuntu user should be
good. Also in yaml file try the ubuntu user.

Same was tested by 4 different labs so far it is working.


Thanks and Regards,
Narinder Gupta (PMP)   narinder.gu...@canonical.com
Canonical, Ltd.narindergupta [irc.freenode.net]
+1.281.736.5150narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com


On Fri, Dec 4, 2015 at 8:35 PM, zhangyuanyou 
wrote:

> Hi  Artur Tyloch,
>I'm working on maas+juju to deploy openstack,now I edit the
> 02-maasdeploy.sh and excute it.
> But this line "maas-deployer -c deployment.yaml -d --force" can't pass ,it
> always let me to input the password like this:
>
> *2015-12-04 17:45:54,032 DEBUG Executing: 'virt-install --connect
> qemu:///system --name opnfv-maas-intel --ram 4096 --vcpus 4 --disk
> vol=default/opnfv-maas-intel-root.img,format=qcow2,bus=virtio,io=native
> --disk
> vol=default/opnfv-maas-intel-seed.img,format=raw,bus=virtio,io=native
> --network bridge=brAdm,model=virtio --network bridge=brData,model=virtio
> --network bridge=brPublic,model=virtio --noautoconsole --vnc --import'
> stdin=''*
> *2015-12-04 17:45:55,145 DEBUG Executing: 'virsh -c qemu:///system
> autostart opnfv-maas-intel' stdin=''*
> *2015-12-04 17:45:55,162 DEBUG Waiting for MAAS vm to come up for ssh..*
> *2015-12-04 17:45:55,163 DEBUG Using ip address specified: 192.168.212.140*
> *2015-12-04 17:45:55,163 DEBUG Executing: 'ssh -i /root/.ssh/id_maas -o
> UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
> root@192.168.212.140  true' stdin=''*
>
>
> *root@192.168.212.140's  password: *I edited the
> file deployment.yaml like this:
> *demo-maas:*
> *maas:*
> *# Defines the general setup for the MAAS environment, including
> the*
> *# username and password for the host as well as the MAAS server.*
> *user: root*
> *password: root*
>
> *# Contains the virtual machine parameters for creating the MAAS
> virtual*
> *# server. Here you can configure the name of the virsh domain,
> the*
> *# parameters for how the network is attached.*
> *name: opnfv-maas-intel*
> *interfaces:
> ['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']*
> *memory: 4096*
> *vcpus: 4*
> *arch: amd64*
> *pool: default*
> *disk_size: 160G*
>
> *# Apt http proxy setting(s)*
> *apt_http_proxy:*
>
> *apt_sources:*
> *  - ppa:maas/stable*
> *  - ppa:juju/stable*
>
> *# Virsh power settings*
> *# Specifies the uri and keys to use for virsh power control of
> the *
> *# juju virtual machine. If the uri is omitted, the value for the*
> *# --remote is used. If no power settings are desired, then do not*
> *# supply the virsh block.*
> *virsh:*
> *rsa_priv_key: /home/ubuntu/.ssh/id_rsa*
> *rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub*
> *#uri: qemu+ssh://ubuntu@10.4.1.1/system
> *
>
> *# Defines the IP Address that the configuration script will use
> to*
> *# to access the MAAS controller via SSH.*
> ip_address: 192.168.212.140
>
> Could you help me to resolve the question ? Any assistance is greatly
> appreciated.
>
> Thanks.
> Yuanyou
>
>
>
>
>
> --
> Juju mailing list
> Juju@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/juju
>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Using maas+juju to deploy openstack, I can't run 02-maasdeploy.sh successfully.

2015-12-04 Thread Billy Olsen 
So what this seems to be indicating is either a) the ssh key isn't properly
setup as part of the MAAS cloud unit script, b) the private key doesn't
match the public key installed, c) something else I can't think of at the
moment.

Can we get the full maas-deployer logs? That may shed some light on what's
going on.

Artur, perhaps something else comes to mind? It's almost as if it's not
fully cleaned up...

Billy

 The maas-deployer should be creating/using the ssh key that's available in
/root/.ssh/id_maas according to the logs, because it's running as root. I
don't currently have access to the script for this (02-maasdeploy.sh) so
I'm not 100% sure of the context you are running this.

If you don't have another maas environment setup on the same host,
something you can try is to remove the /root/.ssh/id_maas* keys

On Friday, December 4, 2015, zhangyuanyou  wrote:

> Hi  Artur Tyloch,
>I'm working on maas+juju to deploy openstack,now I edit the
> 02-maasdeploy.sh and excute it.
> But this line "maas-deployer -c deployment.yaml -d --force" can't pass ,it
> always let me to input the password like this:
>
> *2015-12-04 17:45:54,032 DEBUG Executing: 'virt-install --connect
> qemu:///system --name opnfv-maas-intel --ram 4096 --vcpus 4 --disk
> vol=default/opnfv-maas-intel-root.img,format=qcow2,bus=virtio,io=native
> --disk
> vol=default/opnfv-maas-intel-seed.img,format=raw,bus=virtio,io=native
> --network bridge=brAdm,model=virtio --network bridge=brData,model=virtio
> --network bridge=brPublic,model=virtio --noautoconsole --vnc --import'
> stdin=''*
> *2015-12-04 17:45:55,145 DEBUG Executing: 'virsh -c qemu:///system
> autostart opnfv-maas-intel' stdin=''*
> *2015-12-04 17:45:55,162 DEBUG Waiting for MAAS vm to come up for ssh..*
> *2015-12-04 17:45:55,163 DEBUG Using ip address specified: 192.168.212.140*
> *2015-12-04 17:45:55,163 DEBUG Executing: 'ssh -i /root/.ssh/id_maas -o
> UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
> root@192.168.212.140 
> true' stdin=''*
>
>
> *root@192.168.212.140's
>  password: *I
> edited the file deployment.yaml like this:
> *demo-maas:*
> *maas:*
> *# Defines the general setup for the MAAS environment, including
> the*
> *# username and password for the host as well as the MAAS server.*
> *user: root*
> *password: root*
>
> *# Contains the virtual machine parameters for creating the MAAS
> virtual*
> *# server. Here you can configure the name of the virsh domain,
> the*
> *# parameters for how the network is attached.*
> *name: opnfv-maas-intel*
> *interfaces:
> ['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']*
> *memory: 4096*
> *vcpus: 4*
> *arch: amd64*
> *pool: default*
> *disk_size: 160G*
>
> *# Apt http proxy setting(s)*
> *apt_http_proxy:*
>
> *apt_sources:*
> *  - ppa:maas/stable*
> *  - ppa:juju/stable*
>
> *# Virsh power settings*
> *# Specifies the uri and keys to use for virsh power control of
> the *
> *# juju virtual machine. If the uri is omitted, the value for the*
> *# --remote is used. If no power settings are desired, then do not*
> *# supply the virsh block.*
> *virsh:*
> *rsa_priv_key: /home/ubuntu/.ssh/id_rsa*
> *rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub*
> *#uri: qemu+ssh://ubuntu@10.4.1.1/system
> *
>
> *# Defines the IP Address that the configuration script will use
> to*
> *# to access the MAAS controller via SSH.*
> ip_address: 192.168.212.140
>
> Could you help me to resolve the question ? Any assistance is greatly
> appreciated.
>
> Thanks.
> Yuanyou
>
>
>
>
>


-- 
Billy Olsen

billy.ol...@canonical.com
Software Engineer
Canonical USA
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju

Re: Using maas+juju to deploy openstack, I can't run 02-maasdeploy.sh successfully.

2015-12-04 Thread Narinder Gupta 
For more information about ATT recent setup please follow this link which
works well https://wiki.opnfv.org/copper/academy/joid



Thanks and Regards,
Narinder Gupta (PMP)   narinder.gu...@canonical.com
Canonical, Ltd.narindergupta [irc.freenode.net]
+1.281.736.5150narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com


On Sat, Dec 5, 2015 at 12:34 AM, Narinder Gupta <
narinder.gu...@canonical.com> wrote:

> Hi Yuanyou,
> Will you please let me know your host environment and I am wondering you
> are using root user? I have not tested 02-maasdeploy.sh script with root
> user yet. Will you please try it with ubuntu user?
>
> Will you please try this with latest git repository as i checked in few
> changes recently within couple of days for JOID.
>
> In new version i have added default lab which is very much like you
> are trying the MAAS on.  I tried to configure the ssh appropriately in
> script before i copy the values. So may be running as ubuntu user should be
> good. Also in yaml file try the ubuntu user.
>
> Same was tested by 4 different labs so far it is working.
>
>
> Thanks and Regards,
> Narinder Gupta (PMP)   narinder.gu...@canonical.com
> Canonical, Ltd.narindergupta 
> [irc.freenode.net]+1.281.736.5150
> narindergupta2007[skype]
>
> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
>
>
> On Fri, Dec 4, 2015 at 8:35 PM, zhangyuanyou 
> wrote:
>
>> Hi  Artur Tyloch,
>>I'm working on maas+juju to deploy openstack,now I edit the
>> 02-maasdeploy.sh and excute it.
>> But this line "maas-deployer -c deployment.yaml -d --force" can't
>> pass ,it always let me to input the password like this:
>>
>> *2015-12-04 17:45:54,032 DEBUG Executing: 'virt-install --connect
>> qemu:///system --name opnfv-maas-intel --ram 4096 --vcpus 4 --disk
>> vol=default/opnfv-maas-intel-root.img,format=qcow2,bus=virtio,io=native
>> --disk
>> vol=default/opnfv-maas-intel-seed.img,format=raw,bus=virtio,io=native
>> --network bridge=brAdm,model=virtio --network bridge=brData,model=virtio
>> --network bridge=brPublic,model=virtio --noautoconsole --vnc --import'
>> stdin=''*
>> *2015-12-04 17:45:55,145 DEBUG Executing: 'virsh -c qemu:///system
>> autostart opnfv-maas-intel' stdin=''*
>> *2015-12-04 17:45:55,162 DEBUG Waiting for MAAS vm to come up for ssh..*
>> *2015-12-04 17:45:55,163 DEBUG Using ip address specified:
>> 192.168.212.140*
>> *2015-12-04 17:45:55,163 DEBUG Executing: 'ssh -i /root/.ssh/id_maas -o
>> UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no
>> root@192.168.212.140  true' stdin=''*
>>
>>
>> *root@192.168.212.140's  password: *I edited the
>> file deployment.yaml like this:
>> *demo-maas:*
>> *maas:*
>> *# Defines the general setup for the MAAS environment, including
>> the*
>> *# username and password for the host as well as the MAAS server.*
>> *user: root*
>> *password: root*
>>
>> *# Contains the virtual machine parameters for creating the MAAS
>> virtual*
>> *# server. Here you can configure the name of the virsh domain,
>> the*
>> *# parameters for how the network is attached.*
>> *name: opnfv-maas-intel*
>> *interfaces:
>> ['bridge=brAdm,model=virtio','bridge=brData,model=virtio','bridge=brPublic,model=virtio']*
>> *memory: 4096*
>> *vcpus: 4*
>> *arch: amd64*
>> *pool: default*
>> *disk_size: 160G*
>>
>> *# Apt http proxy setting(s)*
>> *apt_http_proxy:*
>>
>> *apt_sources:*
>> *  - ppa:maas/stable*
>> *  - ppa:juju/stable*
>>
>> *# Virsh power settings*
>> *# Specifies the uri and keys to use for virsh power control of
>> the *
>> *# juju virtual machine. If the uri is omitted, the value for the*
>> *# --remote is used. If no power settings are desired, then do
>> not*
>> *# supply the virsh block.*
>> *virsh:*
>> *rsa_priv_key: /home/ubuntu/.ssh/id_rsa*
>> *rsa_pub_key: /home/ubuntu/.ssh/id_rsa.pub*
>> *#uri: qemu+ssh://ubuntu@10.4.1.1/system
>> *
>>
>> *# Defines the IP Address that the configuration script will use
>> to*
>> *# to access the MAAS controller via SSH.*
>> ip_address: 192.168.212.140
>>
>> Could you help me to resolve the question ? Any assistance is greatly
>> appreciated.
>>
>> Thanks.
>> Yuanyou
>>
>>
>>
>>
>>
>> --
>> Juju mailing list
>> Juju@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
-- 
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/juju