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

Narinder Gupta narinder.gupta at canonical.com
Sat Dec 5 06:50:01 UTC 2015


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.gupta at 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 Sat, Dec 5, 2015 at 12:34 AM, Narinder Gupta <
narinder.gupta at 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.gupta at 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 <zhangyuanyou at 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 at 192.168.212.140 <root at 192.168.212.140> true' stdin=''*
>>
>>
>> *root at 192.168.212.140's <root at 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
>> <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
>>
>>
>>
>>
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20151205/c724a32a/attachment.html>


More information about the Juju mailing list