RE: juju hangs during bootstrapping
Can u try nslookup for archive.ubuntu.com looks like upstream dns issue as well apart from network as you mentioned it was broken. Thanks and regards, Narinder Gupta 1-2817365150 On Sep 30, 2017 04:54, <dave.c...@dell.com> wrote: > Hi Narinder, > > > > Here is the log from the deployed node, actually, I can deploy Operation > System successfully with MAAS or “juju bootstrap” but failed at some final > steps, Our external network is exactly broken for some reason yesterday and > won’t be recovered in short term, but I guess the network broken is > happened after I saw the below error message during bootstrapping. > > “Waiting for address > > Attempting to connect to 10.20.3.254:22” > > > > I can see apt-get update works from the log at the beginning, and the > network is broken couple of hours after I saw those error message. > > > > Does the error message like below has any connection with connection > refused error message? I am not quite sure. > > > > “0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > Fetching Juju agent version 2.2.4 for amd64 > > Attempt 1 to download tools from https://streams.canonical.com/ > juju/tools/agent/2.2.4/juju-2.2.4-ubuntu-amd64.tgz... > > curl: (6) Could not resolve host: streams.canonical.com > > “ > > > > Anyway, I will try it again when our network back to normal, it would be > great if you can see any other issue beside the network, thanks again for > your help! > > > > Best Regards, > > Dave Chen > > > > *From:* Narinder Gupta [mailto:narinder.gu...@canonical.com] > *Sent:* Friday, September 29, 2017 10:52 PM > *To:* Chen2, Dave <dave_ch...@dell.com> > *Cc:* juju <juju@lists.ubuntu.com> > *Subject:* Re: juju hangs during bootstrapping > > > > Hi Dave, > > May I know which division of Dell you are working on? As i have setup > Openstack deployed t Dell multiple time with MAAS and have not seen this > issue so far. > > > > So please send me log /var/log/cloud-init-output.log which will let us > know what is wrong. Also try sudo apt-get update on the bootstrap node to > confirm you have external access. > > > > In MAAS you can always add the ssh keys to land into the installed nodes > though. > > > > > Thanks and Regards, > > Narinder Gupta (PMP) narinder.gu...@canonical.com > > Canonical, Ltd.narindergupta [irc.freenode.net] > > +1.281.736.5150 <(281)%20736-5150> > narindergupta2007[skype] > > > > Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com > > > > On Fri, Sep 29, 2017 at 9:42 AM, <dave.c...@dell.com> wrote: > > Hi All, > > > > I am trying to bootstrap a MAAS cloud based on juju’s official guide ( > https://jujucharms.com/docs/2.2/clouds-maas), everything seems correct > but after the Operation System (Ubuntu 16.04 or Ubuntu14.0) has been > installed, juju hangs when attempting to connect to the MAAS node, here is > what I can see from the terminal, > > > > $ juju bootstrap maas-cloud > > Creating Juju controller "maas-cloud" on maas-cloud > > Looking for packaged Juju agent version 2.2.4 for amd64 > > Launching controller instance(s) on maas-cloud... > > - cka68p (arch=amd64 mem=32G cores=12) > > Fetching Juju GUI 2.9.2 > > Waiting for address > > Attempting to connect to 10.20.3.254:22 (JUJU hangs here!) > > > > And it’s pending here forever, so I tried it again with the debug mode, > > $ juju bootstrap --show-log --debug --bootstrap-series=trusty maas-cloud > maas-cloud-controller > > > > I saw some detail information like below, > > Attempting to connect to 10.20.3.254:22 > > 19:33:11 DEBUG juju.provider.common bootstrap.go:497 connection attempt > for 10.20.3.254 failed: ssh: connect to host 10.20.3.254 port 22: > Connection refused > > 19:33:16 DEBUG juju.provider.common bootstrap.go:497 connection attempt > for 10.20.3.254 failed: ssh: connect to host 10.20.3.254 port 22: > Connection refused > > 19:33:21 DEBUG juju.provider.common bootstrap.go:497 connection attempt > for 10.20.3.254 failed: ssh: connect to host 10.20.3.254 port 22: > Connection refused > > 19:33:56 DEBUG juju.provider.common bootstrap.go:497 connection attempt > for 10.20.3.254 failed: /var/lib/juju/nonce.txt does not exist > > 19:34:32 DEBUG juju.provider.common bootstrap.go:497 connection attempt > for 10.20.3.254 failed: /var/lib/juju/nonce.txt does not exist > > 19:35:08 DEBUG juju.provider.common bootstrap.go:497 connection attempt > for 10.20.3.254 failed: /var/lib/juju/nonce.
Re: Juju 2.1-beta5 is here
Thank you john "": internal-api option help me putting my application with lxd in internal-api network. In that way i can control the applications interface where i want to. I am hoping we will be documenting this knowledge somewhere? 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 Sun, Feb 5, 2017 at 1:21 AM, John Meinel <j...@arbash-meinel.com> wrote: > You're using local charms (./xenial/mongodb) so it's hard to know for sure > exactly what you're deploying without having the full set of files. > > If it is the same as the "official" mongodb: https://jujucharms. > com/mongodb/ > Then it has several bindings that aren't listed in your bundle. Your > bundle states: > > bindings: > internal: internal-api > shared-db: internal-api > public: internal-api > admin: internal-api > > However, the upstream charm https://api.jujucharms. > com/charmstore/v5/mongodb/archive/metadata.yaml has: > nrpe-external-master > database > configsvr > data > benchmark > > mongos-cfg > mongos > > replica-set > > Now, these clearly are slightly different, as the upstream mongodb doesn't > have an "internal", "public", or "admin", and those all look very > suspiciously like very generic bindings on Openstack charms (which may or > may not be relevant on the mongdb charm.) > > I'll also note that "juju deploy" appears to not be strict about > "bindings". If a value listed in bindings matches an endpoint, we will use > it, but we don't warn or fail if a name listed in bundle.yaml doesn't exist. > > However, you can bind all endpoints of a service using "" as the binding > name. So you should be able to do: > > mongodb: > charm: ./xenial/mongodb > num_units: 1 > bindings: > "": internal-api > to: > - "lxd:nodes/0" > > The "" binding will set a default binding for all endpoints in the > application. You should be able to mix it with concrete bindings as well, > so if you wanted to change one of them, you should be able to do (eg): > > mongodb: > charm: ./xenial/mongodb > num_units: 1 > bindings: > "": internal-api > shared-db: admin-api > to: > - "lxd:nodes/0" > > John > =:-> > > > On Sat, Feb 4, 2017 at 2:14 PM, Narinder Gupta < > narinder.gu...@canonical.com> wrote: > >> Hi Nicholas, >> I am finding issues when do the deployment. Bundle i used to deploy with >> juju 2.1-beta4 does not get deployed with juju-2.1-beta5. >> >> Reason of that is mongodb lxd container still waiting to get machine >> which was not the case for juju 2.1-beta4 >> mongodb/0 waiting allocating 0/lxd/3 >> waiting for machine >> >> You can see here http://pastebin.ubuntu.com/23924329/ all services came >> up except mongodb and openfv-promise. I can confirm that if I switch to >> beta4 everything works. Here is the bundle i am deploying >> http://paste.ubuntu.com/23924334/ >> >> >> >> Thanks and Regards, >> Narinder Gupta (PMP) narinder.gu...@canonical.com >> Canonical, Ltd.narindergupta >> [irc.freenode.net]+1.281.736.5150 <(281)%20736-5150> >>narindergupta2007[skype] >> >> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com >> >> >> On Fri, Feb 3, 2017 at 5:54 PM, Nicholas Skaggs < >> nicholas.ska...@canonical.com> wrote: >> >>> The Juju team would like to introduce Juju and conjure-up 2.1-beta5! The >>> most visible changes are to container networking and that juju controllers >>> now expose Prometheus metrics over an HTTPS endpoint. Finally, conjure-up >>> is also a snap, provides juju, and can be installed on trusty as a snap as >>> well! >>> >>> We would especially like feedback on the container networking changes. >>> Do let us know of your experiences, and feel free to open bugs and threads >>> to discuss. >>> >>> ## What’s New in Beta 5 >>> >>> [conjure-up] Now snapped for Trusty and Xenial. >>> [conjure-up] Support for Canonical Kubernetes 1.5.2. >>> [conjure-up] Ability to te
Re: Juju 2.1-beta5 is here
Well this mongodb charm have not changed since trusty. I doubt that binding have been defined for this charm. So I think mechanism to define a default binding for the application where binding is not defined in charms. Also opnfv-promise application does not have any api to consume so here also mechanism to define a default binding for the application will help. 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, Feb 4, 2017 at 12:18 PM, Rick Harding <rick.hard...@canonical.com> wrote: > Narinder, so the beta5 includes the container networking changes that are > required to help make sure that Juju stops guessing bindings incorrectly. > If you look at the error messages in those commands you can see a new error > that the beta5 presents: > > message: 'unable to setup network: no obvious space for > container "0/lxd/10", > host machine has spaces: "admin-api", "external", > "internal-api"' > > This generally means that you need to be explicit in the bindings. I see > in your bundle paste that you have bindinds for each application on machine > 0. I would suggest checking if there are any endpoints that are missing > form the definition? There's a mechanism to define a default binding for > the application, but I'm unable to recall/find that at the moment. I've > /cc'd John who's been working on this and might have another hint for you. > > I'd check the bindings for the ones that don't come up and see if that > helps. > > Rick > > On Sat, Feb 4, 2017 at 1:06 PM Narinder Gupta < > narinder.gu...@canonical.com> wrote: > >> Here you go. >> >> juju status --format yaml >> >> http://paste.ubuntu.com/23927017/ >> >> juju show-machine 0 >> >> http://paste.ubuntu.com/23927020/ >> >> pastebinit bundles.yaml >> >> http://paste.ubuntu.com/23927027/ >> >> Thanks and Regards, >> Narinder Gupta (PMP) narinder.gu...@canonical.com >> Canonical, Ltd.narindergupta >> [irc.freenode.net]+1.281.736.5150 <(281)%20736-5150> >>narindergupta2007[skype] >> >> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com >> >> >> On Sat, Feb 4, 2017 at 9:20 AM, Rick Harding <rick.hard...@canonical.com> >> wrote: >> >> Narinder, can you share the output of juju status --format=yaml and juju >> show-machine 0 >> >> >> On Sat, Feb 4, 2017, 5:15 AM Narinder Gupta <narinder.gu...@canonical.com> >> wrote: >> >> Hi Nicholas, >> I am finding issues when do the deployment. Bundle i used to deploy with >> juju 2.1-beta4 does not get deployed with juju-2.1-beta5. >> >> Reason of that is mongodb lxd container still waiting to get machine >> which was not the case for juju 2.1-beta4 >> mongodb/0 waiting allocating 0/lxd/3 >> waiting for machine >> >> You can see here http://pastebin.ubuntu.com/23924329/ all services came >> up except mongodb and openfv-promise. I can confirm that if I switch to >> beta4 everything works. Here is the bundle i am deploying >> http://paste.ubuntu.com/23924334/ >> >> >> >> Thanks and Regards, >> Narinder Gupta (PMP) narinder.gu...@canonical.com >> Canonical, Ltd.narindergupta >> [irc.freenode.net]+1.281.736.5150 <(281)%20736-5150> >>narindergupta2007[skype] >> >> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com >> >> >> On Fri, Feb 3, 2017 at 5:54 PM, Nicholas Skaggs < >> nicholas.ska...@canonical.com> wrote: >> >> The Juju team would like to introduce Juju and conjure-up 2.1-beta5! The >> most visible changes are to container networking and that juju controllers >> now expose Prometheus metrics over an HTTPS endpoint. Finally, conjure-up >> is also a snap, provides juju, and can be installed on trusty as a snap as >> well! >> >> We would especially like feedback on the container networking changes. Do >> let us know of your experiences, and feel free to open bugs and threads to >> discuss. >> >> ## What’s New in Beta 5 >> >> [conjure-up] Now snapped for Trusty and Xenial. >> [conjure-up] Support for Canonical Kubernetes 1.5.2. >> [con
Re: Juju 2.1-beta5 is here
Here you go. juju status --format yaml http://paste.ubuntu.com/23927017/ juju show-machine 0 http://paste.ubuntu.com/23927020/ pastebinit bundles.yaml http://paste.ubuntu.com/23927027/ 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, Feb 4, 2017 at 9:20 AM, Rick Harding <rick.hard...@canonical.com> wrote: > Narinder, can you share the output of juju status --format=yaml and juju > show-machine 0 > > > On Sat, Feb 4, 2017, 5:15 AM Narinder Gupta <narinder.gu...@canonical.com> > wrote: > >> Hi Nicholas, >> I am finding issues when do the deployment. Bundle i used to deploy with >> juju 2.1-beta4 does not get deployed with juju-2.1-beta5. >> >> Reason of that is mongodb lxd container still waiting to get machine >> which was not the case for juju 2.1-beta4 >> mongodb/0 waiting allocating 0/lxd/3 >> waiting for machine >> >> You can see here http://pastebin.ubuntu.com/23924329/ all services came >> up except mongodb and openfv-promise. I can confirm that if I switch to >> beta4 everything works. Here is the bundle i am deploying >> http://paste.ubuntu.com/23924334/ >> >> >> >> Thanks and Regards, >> Narinder Gupta (PMP) narinder.gu...@canonical.com >> Canonical, Ltd.narindergupta >> [irc.freenode.net]+1.281.736.5150 <(281)%20736-5150> >>narindergupta2007[skype] >> >> Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com >> >> >> On Fri, Feb 3, 2017 at 5:54 PM, Nicholas Skaggs < >> nicholas.ska...@canonical.com> wrote: >> >> The Juju team would like to introduce Juju and conjure-up 2.1-beta5! The >> most visible changes are to container networking and that juju controllers >> now expose Prometheus metrics over an HTTPS endpoint. Finally, conjure-up >> is also a snap, provides juju, and can be installed on trusty as a snap as >> well! >> >> We would especially like feedback on the container networking changes. Do >> let us know of your experiences, and feel free to open bugs and threads to >> discuss. >> >> ## What’s New in Beta 5 >> >> [conjure-up] Now snapped for Trusty and Xenial. >> [conjure-up] Support for Canonical Kubernetes 1.5.2. >> [conjure-up] Ability to teardown models with the new `conjure-down` >> command. >> [juju] Container networking improvements: >> - LXD and KVM guests no longer join all spaces on the host >> machine, but use constraints and bindings to determine what spaces should >> be used >> - Bridges are not created during provisioning, but only created on demand >> for containers that will use them. >> - For clouds other than MAAS, we continue to put containers onlocal >> bridges (lxdbr0) >>[juju] Juju ssh/scp now selects correct address to use to connect to >> the controller. >> [juju] Model config now supports an "extra-info" field for holding >> additional metadata. >> [juju] More memory leaks have been addressed. >> [juju] Stricter rules for validating charm metadata field names to >> conform to data storage requirements. Charm metadata fields can not contain >> dots. >> [juju] controllers now expose HTTPS endpoints under >> “/introspection/”, accessible to controller superusers, and users with read >> access to the controller model:/introspection/debug/pprof/profile, >> /introspection/depengine/,/introspection/metrics. >> >> >> ## Bugs Addressed >> >> Check the milestones for a detailed breakdown of juju and conjure-up bugs >> corrected. >> >> https://launchpad.net/juju/+milestone/2.1-beta5 >> >> https://github.com/conjure-up/conjure-up/milestone/14?closed=1 >> >> ## How do I get it? >> >> If you are running Ubuntu, you can get Juju from the juju devel ppa: >> >>sudo add-apt-repository ppa:juju/devel; sudo apt-get update >> >>sudo apt-get install juju >> >> Or install Juju from the snap store: >> >>snap install juju --beta --devmode >> >> Install conjure-up from the snap store: >> >> snap install conjure-up --classic --beta >> >> If you are on Trusty, you'll need to run a few extra commands: >>sudo apt-get install snapd >>sudo groupadd lxd &am
Re: Juju 2.1-beta5 is here
Hi Nicholas, I am finding issues when do the deployment. Bundle i used to deploy with juju 2.1-beta4 does not get deployed with juju-2.1-beta5. Reason of that is mongodb lxd container still waiting to get machine which was not the case for juju 2.1-beta4 mongodb/0 waiting allocating 0/lxd/3 waiting for machine You can see here http://pastebin.ubuntu.com/23924329/ all services came up except mongodb and openfv-promise. I can confirm that if I switch to beta4 everything works. Here is the bundle i am deploying http://paste.ubuntu.com/23924334/ 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, Feb 3, 2017 at 5:54 PM, Nicholas Skaggs < nicholas.ska...@canonical.com> wrote: > The Juju team would like to introduce Juju and conjure-up 2.1-beta5! The > most visible changes are to container networking and that juju controllers > now expose Prometheus metrics over an HTTPS endpoint. Finally, conjure-up > is also a snap, provides juju, and can be installed on trusty as a snap as > well! > > We would especially like feedback on the container networking changes. Do > let us know of your experiences, and feel free to open bugs and threads to > discuss. > > ## What’s New in Beta 5 > > [conjure-up] Now snapped for Trusty and Xenial. > [conjure-up] Support for Canonical Kubernetes 1.5.2. > [conjure-up] Ability to teardown models with the new `conjure-down` > command. > [juju] Container networking improvements: > - LXD and KVM guests no longer join all spaces on the host > machine, but use constraints and bindings to determine what spaces should > be used > - Bridges are not created during provisioning, but only created on demand > for containers that will use them. > - For clouds other than MAAS, we continue to put containers onlocal > bridges (lxdbr0) >[juju] Juju ssh/scp now selects correct address to use to connect to > the controller. > [juju] Model config now supports an "extra-info" field for holding > additional metadata. > [juju] More memory leaks have been addressed. > [juju] Stricter rules for validating charm metadata field names to > conform to data storage requirements. Charm metadata fields can not contain > dots. > [juju] controllers now expose HTTPS endpoints under “/introspection/”, > accessible to controller superusers, and users with read access to the > controller model:/introspection/debug/pprof/profile, > /introspection/depengine/,/introspection/metrics. > > > ## Bugs Addressed > > Check the milestones for a detailed breakdown of juju and conjure-up bugs > corrected. > > https://launchpad.net/juju/+milestone/2.1-beta5 > > https://github.com/conjure-up/conjure-up/milestone/14?closed=1 > > ## How do I get it? > > If you are running Ubuntu, you can get Juju from the juju devel ppa: > >sudo add-apt-repository ppa:juju/devel; sudo apt-get update > >sudo apt-get install juju > > Or install Juju from the snap store: > >snap install juju --beta --devmode > > Install conjure-up from the snap store: > > snap install conjure-up --classic --beta > > If you are on Trusty, you'll need to run a few extra commands: >sudo apt-get install snapd >sudo groupadd lxd && sudo usermod -a -G lxd $USER >sudo reboot > > Now you can install snaps, including conjure-up, as normal: >snap install conjure-up --classic --beta > > Windows, Centos, and macOS users can get a corresponding Juju installer at: > >https://launchpad.net/juju/+milestone/2.1-beta5 > > ## Feedback Appreciated! > > We encourage everyone to let us know how you’re using Juju. Send us a > message on Twitter using #jujucharms, join us at #juju on freenode, and > subscribe to the mailing list at juju@lists.ubuntu.com. > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm > an/listinfo/juju > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju bootstrap complaining about "no registered provider for"
Hi juju Team,
Lenovo team is trying to write a new provider with their xclarity product.
Currently they are experimenting it mock-provider and did some coding and
trying to bootstrap the nodes and facing few issues.
Do you think we can give Lenovo team some guidance on how to write a new
provider? Also can rectify current issues.
Hi Fang,
Happy new year.
juju-...@lists.ubuntu.com is the correct mailing list you can pose your
questions about juju providers. Also you can always connect to irc channel
#juju.
Thanks and Regards,
Narinder Gupta (PMP) narinder.gu...@canonical.com
Canonical, Ltd.narindergupta
[irc.freenode.net]+1.281.736.5150 <(281)%20736-5150>
narindergupta2007[skype]
Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com
On Tue, Jan 3, 2017 at 3:50 PM, Feng Xia1 <fx...@lenovo.com> wrote:
>
>
> Hi Narinder,
>
>
>
> Happy new year!
>
>
>
> I’m on the path of getting deeper into the juju providers. I put together
> a mock-up provider, issued “juju bootstrap”, manually started a VM with the
> IP that juju bootstrap is expecting, and manually put correct nonce.txt on
> that VM.
>
>
>
> By this point, juju deploy command happily ssh-ed into this VM, started
> cloud-init scripts. Everything is good until at the end I get this error:
>
>
> “no registered provider for…”
>
>
>
> The error message came from juju/juju/environs/config.go, function “func
> (r *globalProviderRegistry) Provider(providerType string) (EnvironProvider,
> error) {…”. However, the global registry does have an entry for each of the
> cloud types.
>
>
>
> What did I miss?
>
>
>
> [image:
> http://lenovocentral.lenovo.com/marketing/branding/email_signature/images/gradient.gif]
>
> *Feng xia*
> Engineer
> Lenovo USA
>
> [image: Phone]5088011794 <(508)%20801-1794>
> [image: Email]fx...@lenovo.com <fx...@lenovo.com>
>
>
>
> Lenovo.com <http://www.lenovo.com/>
> Twitter <http://twitter.com/lenovo> | Facebook
> <http://www.facebook.com/lenovo> | Instagram
> <https://instagram.com/lenovo> | Blogs <http://blog.lenovo.com/> | Forums
> <http://forums.lenovo.com/>
>
> [image: ImageLogo-Holiday-Lights]
>
>
>
>
>
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju status show blank for public name for one machine.
Stuart, On bare metal I can reproduce it 4 out of 5 times. I have system already in failed state in case you wants to debug. Ping me for access details. 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 Wed, Jul 6, 2016 at 8:46 AM, Stuart Bishop <stuart.bis...@canonical.com> wrote: > On 6 July 2016 at 20:16, Narinder Gupta <narinder.gu...@canonical.com> > wrote: > > Well I have created the bug > > https://bugs.launchpad.net/juju-core/+bug/1599507 and attached the logs > of > > physical node where issue was seen. > > I think this is a dupe of > https://bugs.launchpad.net/juju-core/+bug/1534757 (which expired, as I > had not been able to reproduce it). > > -- > Stuart Bishop <stuart.bis...@canonical.com> > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju status show blank for public name for one machine.
Well I have created the bug https://bugs.launchpad.net/juju-core/+bug/1599507 and attached the logs of physical node where issue was seen. 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 Wed, Jul 6, 2016 at 8:01 AM, Narinder Gupta <narinder.gu...@canonical.com > wrote: > James, > I am able to reproduce this issue. You can connect to this environment to > have a look in case you want to debug? Please ping me on IRC to get the > detailed information. > > 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 Mon, Jul 4, 2016 at 5:51 AM, James Tunnicliffe < > james.tunnicli...@canonical.com> wrote: > >> Hi Narinder, >> >> Do you have logs from a failed deployment? The best thing to do when >> something is stuck like this is open a bug and attach a couple of nice >> big tarballs of everything from /var/log/juju from machines 0 and the >> unhappy units/machines (in your case machine 2) so one of us can take >> a look. >> >> Thanks, >> >> James >> >> On 1 July 2016 at 22:51, Narinder Gupta <narinder.gu...@canonical.com> >> wrote: >> > I am seeing strange behavior with juju 1.25.5 recently. >> > >> > http://pastebin.ubuntu.com/18269577/ >> > >> > you can see machine 2 in pending state while in MAAS it was deployed. >> But >> > being in pending state you can see container on the machine 2 have >> started >> > installing charm. I am seeing this from last week onward and at end >> > deployment failed. >> > >> > After some time install failure but container installation is still >> > progress. >> > >> > http://pastebin.ubuntu.com/18269692/ >> > >> > 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 >> > >> > >> > -- >> > 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 >> > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju status show blank for public name for one machine.
I am seeing strange behavior with juju 1.25.5 recently. http://pastebin.ubuntu.com/18269577/ you can see machine 2 in pending state while in MAAS it was deployed. But being in pending state you can see container on the machine 2 have started installing charm. I am seeing this from last week onward and at end deployment failed. After some time install failure but container installation is still progress. http://pastebin.ubuntu.com/18269692/ 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 -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Planning for Juju 2.2 (16.10 timeframe)
+1 for DNS as this was request in other community project as well which uses JUJU. 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, Apr 5, 2016 at 2:50 PM, Merlijn Sebrechts < merlijn.sebrec...@gmail.com> wrote: > +1 for the DNS; We could really use that! > > 2016-04-05 3:31 GMT-07:00 Simon Davy <simon.d...@canonical.com>: > >> Lots of interesting ideas here. >> >> Some other ideas (apologies if these have already been proposed, but I >> don't *think* they have) >> >> a) A small one - please can we have 'juju get '? See >> https://bugs.launchpad.net/juju-core/+bug/1423548 >> >> Maybe this is already in the config schema work, but it would *really* >> help in a lot >> of situations, and it seems simple? >> >> e.g. >> >> $ juju get my-service foo >> bar >> >> This would make me very happy :) >> >> >> b) A bigger ask: DNS for units. >> >> Provider level dns (when present) only gives machine name dns, which >> is not useful when working at the model level. As an operator, I've >> generally no idea which machine unit X is on, and have to go hunting >> in juju status. It's be great to be able to address individual units, both >> manually when troubleshooting, and in scripts. >> >> One way to do this might be if juju could provide a local dns resolver >> as part of the controller. >> >> e.g. if you have a model called 'bar', with service called >> 'foo', with 2 units, the following domains[1] could be resolved by the >> controller dns resolver: >> >> foo-0.bar >> foo-1.bar >> >> and/or >> >> unit-foo-0.bar >> unit-foo-1.bar >> >> or even >> >> 0.foo.bar >> 1.foo.bar >> >> >> Then tools can be configured to use this dns resolver. For example, we >> have deployment servers where we manage our models from. We could add >> the controller's dns here, making it easy for deployment/maintenance >> scripts to target units easily. >> >> Right now, we have to parse json output in bash from juju status to >> scrape ip addresses, which is horrible[2] >> >> Other possibilities (warning: not necessarily a good idea) >> >> * add this resolver into the provisioned machine configuration, so config >> on the units could use these domain names. >> >> * the controller dns resolver can forward to a specified upstream >> resolver (falling back to host's resolv.conf info) >> - single point of control for dns for all models in that controller >> - repeatability/reliability - if upsteam dns is down, controller >> dns still provides local resolution, and also could cache upstream, >> perhaps. >> >> * if you ask for a service level address, rather than unit, it could >> maybe return a dns round robin record. This would be useful for >> internal haproxy services, for example, and could give some default >> load-balancing OOTB >> >> * would provide dns on providers that don't have native support >> (like, erm, ps4.5 :) >> >> Now, there are caveats a plenty here. We'd need HA dns cluster, and >> there's a whole bunch of security issues that would need addressing, >> to be sure. And I would personally opt for an implementation that uses >> proven dns technology rather than implementing a new dns >> resolver/forwarder in go with a mongodb backend. But maybe that's just >> me ;P >> >> >> Thanks. >> >> >> [1] in hindsight, I do think having a / in the unit name was not the >> best option, due to it's path/url issues. AIUI, internally juju uses >> unit--N as identifiers? Could this be exposed as alternate unit >> names? i.e. cli/api commands could accept either? >> >> [2] At the very least, it would be great to have a cli to get the >> ip(s) of a unit, would simplify a lot of scripts. e.g. >> >> $ juju get-ip foo/0 --private >> 10.0.3.24 >> $ juju get-ip foo/0 --public >> 1.2.3.4 >> $ juju get-ip foo --private >> 10.0.3.24 >> 10.0.3.134 >> >> >> -- >> Simon >> >> -- >> 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 > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Is whether Joid support L3?
Hi all, Canonical has holidays till end of this year. But answer to your question is yes here odl supoort l3 and l2 is supported by neutron. Ext port is mentioned in the bundle and set in 01-deploybundle.sh for each sdn for each lab. For some labs its eth1 and for some lab eth2.724 basically its public network define in pharos specs. Joid release is tie up with opnfv release. As joid uses juju and Maas which has already released and I don't think so you need to modify juju. Thanks and regards, Narinder Gupta 1-2817365150 On Dec 25, 2015 05:13, "zhangyuanyou" <zhangyuan...@huawei.com> wrote: > Hi Narinder Gupta, > > Now I am working on Joid ,I want to know is whether Joid support L3 now? > > And If Joid support L3, do we have a port to visit external network? > > Could u tell me the release plan of Joid? Time is limited. > > Cherry Christmas! > > Thanks, > > Yuanyou > > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Liberty create vm instance error?
yeah without ODL i am also facing the same issue with nosdn bundle. I am verifying it and let you know soon once find a fix. But old bundle is working fine. So please try the old bundle and see? 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 18, 2015 at 8:55 PM, zhangyuanyou <zhangyuan...@huawei.com> wrote: > Hi ,Narinder Gupta > > When I use ./deploy.sh to deploy openstack liberty successfully,but I > still can’t create vm instance successfully. > > I checked the services, only cinder-volume,cinder-scheduler are status > Down, other services is all up. > > And I find some error in the log: > > 2015-12-17 08:29:23.585 24614 INFO nova.virt.driver [-] Loading compute > driver 'libvirt.LibvirtDriver' > > 2015-12-17 08:29:23.604 24614 INFO oslo_service.periodic_task [-] Skipping > periodic task _periodic_update_dns because its interval is negative > > 2015-12-17 08:29:23.654 24614 INFO oslo.messaging._drivers.impl_rabbit > [req-25d3f09c-b376-460c-8ac2-2a5fe4e2e14f - - - - -] Connecting to AMQP > server on localhost:5672 > > 2015-12-17 08:29:23.662 24614 ERROR oslo.messaging._drivers.impl_rabbit > [req-25d3f09c-b376-460c-8ac2-2a5fe4e2e14f - - - - -] AMQP server on > 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in > 1 seconds. > > 2015-12-17 08:29:24.671 24614 ERROR oslo.messaging._drivers.impl_rabbit > [req-25d3f09c-b376-460c-8ac2-2a5fe4e2e14f - - - - -] AMQP server on > 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in > 2 seconds. > > 2015-12-17 08:29:26.680 24614 ERROR oslo.messaging._drivers.impl_rabbit > [req-25d3f09c-b376-460c-8ac2-2a5fe4e2e14f - - - - -] AMQP server on > 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in > 2 seconds. > > > > > > Thanks and best wishes, > > yuanyou > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: 答复: 答复: After run 02-maasdeploy.sh successfully,the bootstrap is shutdown
Looks like its pxe booted but commissioning failed. Will you please check the reason of failure? Is it still power management or some other reason? Thanks and regards, Narinder Gupta 1-2817365150 On Dec 12, 2015 04:14, "zhangyuanyou" <zhangyuan...@huawei.com> wrote: > Hi Narinder Gupta, > > I have use the new code to deploy,but the bootstrap, > node1-controller,node2-compute is still shutoff. > > I use vnc to login the bootstrap,and saw the vm start,but soon it will > shutdown : > > > > So, the maas can’t dectect the bootstrap,controller,computer, still fail > commissioning. > > > > Thanks, > > Yuanyou > > > > > > *发件人:* Narinder Gupta [mailto:narinder.gu...@canonical.com] > *发送时间:* 2015年12月12日 10:33 > *收件人:* zhangyuanyou > *抄送:* Billy Olsen; juju@lists.ubuntu.com; wuwenbin; jiangrui (D); > artur.tyl...@canonical.com > *主题:* Re: 答复: After run 02-maasdeploy.sh successfully,the bootstrap is > shutdown > > > > Looks like your bootstrap VMS can't pxe boot. Does all your machines are > using virbrO if yes there could be another dhcp enable on that bridge. You > might need to disable dhcp on that bridge. For virtual machines on virbr0 I > am working on scripts to do that. > > Thanks and regards, > Narinder Gupta > 1-2817365150 > > On Dec 11, 2015 20:10, "zhangyuanyou" <zhangyuan...@huawei.com> wrote: > > Hi, Narinder Gupta > > I can use vnc to login the bootstrap ,but it shows like the boot.bmp,boot > failed:not a bootable disk. > > Could you tell me how to deal with the error? > > > > Thanks, > > yuanyou > > *发件人:* Narinder Gupta [mailto:narinder.gu...@canonical.com] > *发送时间:* 2015年12月11日 18:19 > *收件人:* zhangyuanyou > *抄送:* artur.tyl...@canonical.com; billy.ol...@canonical.com; > juju@lists.ubuntu.com; jiangrui (D); wuwenbin > *主题:* Re: After run 02-maasdeploy.sh successfully,the bootstrap is > shutdown > > > > can you look into node details and see why it failed to commissioning? > > > 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 11, 2015 at 4:10 AM, zhangyuanyou <zhangyuan...@huawei.com> > wrote: > > Hi ,Narinder Gupta > >Now I have excute the 02-maasdeploy.sh successfully,but I saw the > bootstrap is shutdown, > > Even I start the bootstrap,the maas server still can’t detect the > bootstrap.I don’t know why? > > From the maas GUI,the tab Nodes shows bootstrap fail to commsioning. > > Thanks, > > yuanyou > > > -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: 答复: After run 02-maasdeploy.sh successfully,the bootstrap is shutdown
Looks like your bootstrap VMS can't pxe boot. Does all your machines are using virbrO if yes there could be another dhcp enable on that bridge. You might need to disable dhcp on that bridge. For virtual machines on virbr0 I am working on scripts to do that. Thanks and regards, Narinder Gupta 1-2817365150 On Dec 11, 2015 20:10, "zhangyuanyou" <zhangyuan...@huawei.com> wrote: > Hi, Narinder Gupta > > I can use vnc to login the bootstrap ,but it shows like the boot.bmp,boot > failed:not a bootable disk. > > Could you tell me how to deal with the error? > > > > Thanks, > > yuanyou > > *发件人:* Narinder Gupta [mailto:narinder.gu...@canonical.com] > *发送时间:* 2015年12月11日 18:19 > *收件人:* zhangyuanyou > *抄送:* artur.tyl...@canonical.com; billy.ol...@canonical.com; > juju@lists.ubuntu.com; jiangrui (D); wuwenbin > *主题:* Re: After run 02-maasdeploy.sh successfully,the bootstrap is > shutdown > > > > can you look into node details and see why it failed to commissioning? > > > 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 11, 2015 at 4:10 AM, zhangyuanyou <zhangyuan...@huawei.com> > wrote: > > Hi ,Narinder Gupta > >Now I have excute the 02-maasdeploy.sh successfully,but I saw the > bootstrap is shutdown, > > Even I start the bootstrap,the maas server still can’t detect the > bootstrap.I don’t know why? > > From the maas GUI,the tab Nodes shows bootstrap fail to commsioning. > > 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.
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
Re: if the openstack liberty is supported by juju
Yes liberty is supported by juju for trusty as well as willy version of Ubuntu. We already have three labs up and running with juju and working with other to complete the integration with other labs. Thanks and regards, Narinder Gupta 1-2817365150 On Dec 7, 2015 03:29, "zhangyuanyou" <zhangyuan...@huawei.com> wrote: > Hi Artur Tyloch, >I want to know if the openstack liberty is supported by juju? > > Now I’m working on the juju installing,should I use openstack liberty? > > 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.
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 <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 <root@192.168.212.140> true' stdin=''* > > > *root@192.168.212.140's <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 > <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@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.
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 <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 <root@192.168.212.140> true' stdin=''* >> >> >> *root@192.168.212.140's <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 >> <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@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: After deploying openstack,I can't create vm instance
Yuanyou ZHANG, Looks like you are having the similar issue which I find during my testing with kilo in OPNFV and logged bug under rabbitmq-server https://bugs.launchpad.net/charms/+source/rabbitmq-server/+bug/1506642 . Only workaround is to restart the rabbitmq, nova-conductor and nova-compute services. But after some time we observed the same issue again. After moving to Liberty Openstack we are not observing this behavior. 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 Wed, Dec 2, 2015 at 9:04 PM, zhangyuanyou <zhangyuan...@huawei.com> wrote: > Hi Artur Tyloch, > I'm working on deploying openstack-kilo using Juju,now I can deploy > openstack successfully and create network in openstack-dashboard. > > But when I create a vm instance, I find the nova-compute shutdown. > I login the controller node and show the nova service-list,I find there is > not nova-consoleauth. > So I do this: apt-get install nova-consoleauth,but how can I reboot the > nova-compute? Any assistance is greatly appreciated. > > ++++--+-+---++-+ > | Id | Binary | Host | Zone | Status | > State | Updated_at | Disabled Reason | > > ++++--+-+---++-+ > | 1 | nova-cert | onos-local-machine-1-lxc-3 | internal | enabled | > up| 2015-12-02T09:56:38.00 | - | > | 2 | nova-conductor | onos-local-machine-1-lxc-3 | internal | enabled | > up| 2015-12-02T09:56:39.00 | - | > | 3 | nova-scheduler | onos-local-machine-1-lxc-3 | internal | enabled | > up| 2015-12-02T09:56:39.00 | - | > | 4 | nova-compute | onos-local-machine-3 | nova | enabled | > down | 2015-12-02T09:47:43.00 | - | > > ++++--+-+---++-+ > > nova-conductor.log: > 2015-12-02 08:59:00.341 11084 INFO nova.openstack.common.service > [req-6d38fc33-712f-4b12-83d0-d4399e870a5e - - - - -] Started child 11249 > 2015-12-02 08:59:00.348 11084 INFO nova.openstack.common.service > [req-6d38fc33-712f-4b12-83d0-d4399e870a5e - - - - -] Started child 11250 > 2015-12-02 08:59:00.358 11248 INFO nova.service [-] Starting conductor > node (version 2015.1.2) > 2015-12-02 08:59:00.358 11084 INFO nova.openstack.common.service > [req-6d38fc33-712f-4b12-83d0-d4399e870a5e - - - - -] Started child 11251 > 2015-12-02 08:59:00.367 11250 INFO nova.service [-] Starting conductor > node (version 2015.1.2) > 2015-12-02 08:59:00.367 11249 INFO nova.service [-] Starting conductor > node (version 2015.1.2) > 2015-12-02 08:59:00.372 11251 INFO nova.service [-] Starting conductor > node (version 2015.1.2) > 2015-12-02 08:59:00.413 11084 WARNING oslo_config.cfg > [req-6d38fc33-712f-4b12-83d0-d4399e870a5e - - - - -] Option "lock_path" > from group "DEFAULT" is deprecated. Use option "lock_path" from group > "oslo_concurrency". > 2015-12-02 08:59:00.734 11244 INFO oslo_messaging._drivers.impl_rabbit > [req-70fa0b3e-71d8-4171-9d63-83757938f02d - - - - -] Connecting to AMQP > server on localhost:5672 > 2015-12-02 08:59:00.753 11244 ERROR oslo_messaging._drivers.impl_rabbit > [req-70fa0b3e-71d8-4171-9d63-83757938f02d - - - - -] AMQP server on > 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in > 1 seconds. > 2015-12-02 08:59:00.774 11247 INFO oslo_messaging._drivers.impl_rabbit > [req-2447759d-c90b-41d0-90a0-ec7a23551b86 - - - - -] Connecting to AMQP > server on localhost:5672 > 2015-12-02 08:59:00.778 11245 INFO oslo_messaging._drivers.impl_rabbit > [req-7db8bff8-46ae-4f14-ad0a-11506c858369 - - - - -] Connecting to AMQP > server on localhost:5672 > 2015-12-02 08:59:00.783 11247 ERROR oslo_messaging._drivers.impl_rabbit > [req-2447759d-c90b-41d0-90a0-ec7a23551b86 - - - - -] AMQP server on > 127.0.0.1:5672 is unreachable: [Errno 111] ECONNREFUSED. Trying again in > 1 seconds. > 2015-12-02 08:59:00.783 11242 INFO oslo_messaging._drivers.impl_rabbit > [req-a0bab9d4-e8c4-4674-9fd9-d355a7137a1a - - - - -] Connecting to AMQP > server on localhost:5672 > 2015-12-02 08:59:00.787 11245 ERROR oslo_messaging._drivers.impl_rabbit > [req-7db8bff8-46ae-4f14-ad0a-11506c858369 - - - - -] AMQP server on > 127.0.0.1:5672 is unreachable: [Errno
Re: Static IP addressing? with Mellanox
Indeed, the IPoIB is part of the Mellanox charm work, as well as the driver work underneath it all. We are also pursuing Ceph/RDMA with Mellanox and I'm sure it will also appear in our Intel relationship. charms are available at https://code.launchpad.net/~mellanox-canonical 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, Nov 17, 2015 at 1:31 PM, Mark Shuttleworth <m...@ubuntu.com> wrote: > On 17/11/15 10:38, ed bond wrote: > > I honestly think ceph/neutron having RDMA support would be more > important. I figured I could hack together IPoIB quicker since it was an > Operating System layer and not changing all the Open Stack charms. > > I believe this work is in progress between Mellanox and Canonical. > > Mark > > -- > 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
