Re: adding nics to a vm in vmware built by juju deploy
Our VMWare Vcenter is running version 6.5. There are 2 sets of tools, one in flash which is supposed to be going away and one in html5. The html5 version doesn't support all of the features it needs to yet. The html5 views the juju created vms as locked, but the flash version allows us to edit them as needed. We work with the tools that are available and throw out ideas for features that would improve it. Love the juju tools! Great work everyone! On Tue, 2018-06-19 at 08:49 -0400, Rick Harding wrote: > I'm not familiar if there's any way to unlock/force through VMWare > but Juju doesn't currently support the idea of adding nics to running > instances at this moment. It's something we're definitely looking for > the future as clouds do support things like hot plugging nics. It > might be worth a test to see if you can adjust the nics on the VMWare > side. In some cases you can work around Juju like adding storage to > the root disk by upgrading the instance through the cloud tooling. > > On Fri, Jun 8, 2018 at 7:58 AM Daniel Bidwell > wrote: > > I have a vmware server that I am using as the target for deploying > > vms > > with juju. I have a set of vms that need multiple nics on > > different > > vlans/vmware networks. I want the vm to be on the primary network, > > but > > also have nics for 4 other secondary networks. > > > > Once the vm is deployed, vmware considers it locked and will not > > let me > > add additional nics. Is there a way to unlock it? Or is there a > > way > > to deploy the vm with the nics installed from the start? > > > > I didn't see anything in the online docs about adding additional > > networks to the constraints clause of the deploy. If this feature > > is > > not available at this time, could it be considered for the future? > > -- > > Daniel Bidwell > > > > > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: How do you clean a juju disk or make it larger?
My case was using VmWare as the cloud. The controllers defaulted to 10GB. I am running juju 2.3.8. I have about 12 vm's on the controller with about 24 locally written charms. /var/lib/juju/db is currently using 8.3GB. The simplest solution for me was to increase the root disk size and reboot the controller. The cloud-init process resized the partition to fill the rest of the disk and then resized the file system to fill the enlarged partition. I am not concerned about the size so much as I needed to finish deploying my spread of servers. I did clean out a group of old kernels that had accumulated as well as old versions of juju that I had upgraded from, but those were incidental. I posted the question and solution to askubuntu.com so others could find the answer easily if they hit the same problem. On Wed, 2018-06-13 at 16:06 +0400, John Meinel wrote: > IIRC older Juju used the default EC2 settings, which gave 8GB hard > drives, but newer should default to 32GB disks. I'm not sure how that > varies across all providers, though. > > Note that you should always be able to bootstrap with a custom root- > disk constraint. eg "juju bootstrap --bootstrap-constraints root- > disk=32G" > > As for issues about the disk filling up, it would be good to have a > bit more information about what juju version, what types of workloads > you're deploying, etc. The data might be stale charm binaries that > are being cached by the server, or if it is Juju 1.X then it could be > image caches, or transaction log issues, etc. > > John > =:-> > > On Tue, Jun 12, 2018 at 9:12 AM, Paul Gear > wrote: > > On 11/06/18 01:47, Daniel Bidwell wrote: > > > My juju controllers appear to be defaulting to a 10GB root disk. > > I am > > > running out of disk space on the controller. I have 6.7GB in > > > /var/lib/juju/db. Is there a way to reduce the disk usage on > > this? > > > > I think perhaps this is worth logging as a wishlist bug. A long- > > running > > production juju controller should never be deployed with a disk > > that > > small (our largest production cluster is already a little > > uncomfortable > > with 50 GB), and juju doesn't really distinguish between "this is a > > CI > > controller that's only going to be up long enough to run my test > > suite" > > and "this is going to run all of my production OpenStack VMs for > > the > > next year". It would be nice if you could tell it "size the > > controller > > for N live models". > > > > > If not, can I make the root disk larger? What are my options? > > > > That all depends on your underlying cloud infrastructure. I > > believe > > some providers (e.g. GCE) make this really easy. > > > > > I have already cleared out kernel updates. > > > > Not directly related to juju controller sizing, but relevant to the > > above: I've been working on a little tool that handles many of the > > common scenarios we encounter, including kernel updates and other > > tools > > you may or may not use. It's alpha quality; feedback & patches > > gratefully accepted: > > > > https://code.launchpad.net/~paulgear/+git/cleanup > > > > -- > > Regards, > > Paul Gear > > Site Reliability Engineer > > Canonical - Information Systems > > > > > > -- > > Juju mailing list > > Juju@lists.ubuntu.com > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman > > /listinfo/juju > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
How do you clean a juju disk or make it larger?
My juju controllers appear to be defaulting to a 10GB root disk. I am running out of disk space on the controller. I have 6.7GB in /var/lib/juju/db. Is there a way to reduce the disk usage on this? If not, can I make the root disk larger? What are my options? I have already cleared out kernel updates. -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
adding nics to a vm in vmware built by juju deploy
I have a vmware server that I am using as the target for deploying vms with juju. I have a set of vms that need multiple nics on different vlans/vmware networks. I want the vm to be on the primary network, but also have nics for 4 other secondary networks. Once the vm is deployed, vmware considers it locked and will not let me add additional nics. Is there a way to unlock it? Or is there a way to deploy the vm with the nics installed from the start? I didn't see anything in the online docs about adding additional networks to the constraints clause of the deploy. If this feature is not available at this time, could it be considered for the future? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
More juju upgrade-juju failings
I am running on juju 2.3.3-xenial-amd64 and my controllers are running
in VMware Vsphere with version 2.3.2. I thought that it would be a
good thing for me to upgrade the controllers.
I have a controller, "juju switch" generates:
bannercontroller:admin/default
and juju status generates:
ModelControllerCloud/Region Version SLA
default bannercontroller myvscloud/New Datacenter 2.3.2unsupported
App Version Status Scale Charm Store Rev OS Notes
Unit Workload Agent Machine Public address Ports Message
Machine State DNS Inst id Series AZ Message
doing "juju upgrade-juju --agent-version 2.3.3 --debug" generates:
17:16:19 INFO juju.cmd supercommand.go:56 running juju [2.3.3 gc go1.9.2]
17:16:19 DEBUG juju.cmd supercommand.go:57 args:
[]string{"/snap/juju/3452/bin/juju", "upgrade-juju", "--agent-version",
"2.3.3", "--debug"}
17:16:19 INFO juju.juju api.go:67 connecting to API addresses:
[10.1.61.239:17070]
17:16:19 DEBUG juju.api apiclient.go:843 successfully dialed
"wss://10.1.61.239:17070/model/5a057215-e835-42fb-8c5a-f9d57eded74c/api"
17:16:19 INFO juju.api apiclient.go:597 connection established to
"wss://10.1.61.239:17070/model/5a057215-e835-42fb-8c5a-f9d57eded74c/api"
17:16:19 INFO juju.juju api.go:67 connecting to API addresses:
[10.1.61.239:17070]
17:16:19 DEBUG juju.api apiclient.go:843 successfully dialed
"wss://10.1.61.239:17070/model/5a057215-e835-42fb-8c5a-f9d57eded74c/api"
17:16:19 INFO juju.api apiclient.go:597 connection established to
"wss://10.1.61.239:17070/model/5a057215-e835-42fb-8c5a-f9d57eded74c/api"
17:16:19 INFO juju.juju api.go:67 connecting to API addresses:
[10.1.61.239:17070]
17:16:19 DEBUG juju.api apiclient.go:843 successfully dialed
"wss://10.1.61.239:17070/api"
17:16:19 INFO juju.api apiclient.go:597 connection established to
"wss://10.1.61.239:17070/api"
17:16:19 DEBUG juju.cmd.juju.commands upgradejuju.go:466 searching for agent
binaries with major: 2
17:16:22 INFO cmd upgradejuju.go:363 available agent binaries:
2.3.3-artful-amd64
2.3.3-artful-arm64
2.3.3-artful-ppc64el
2.3.3-artful-s390x
2.3.3-bionic-amd64
2.3.3-bionic-arm64
2.3.3-bionic-ppc64el
2.3.3-bionic-s390x
2.3.3-centos7-amd64
2.3.3-trusty-amd64
2.3.3-trusty-arm64
2.3.3-trusty-ppc64el
2.3.3-trusty-s390x
2.3.3-win10-amd64
2.3.3-win2012-amd64
2.3.3-win2012hv-amd64
2.3.3-win2012hvr2-amd64
2.3.3-win2012r2-amd64
2.3.3-win2016-amd64
2.3.3-win2016nano-amd64
2.3.3-win7-amd64
2.3.3-win8-amd64
2.3.3-win81-amd64
2.3.3-xenial-amd64
2.3.3-xenial-arm64
2.3.3-xenial-ppc64el
2.3.3-xenial-s390x
best version:
2.3.3
17:16:22 DEBUG juju.api monitor.go:35 RPC connection died
17:16:22 DEBUG juju.api monitor.go:35 RPC connection died
17:16:22 DEBUG juju.api monitor.go:35 RPC connection died
ERROR a hosted model cannot have a higher version than the server model: 2.3.3
> 2.3.2
17:16:22 DEBUG cmd supercommand.go:459 error stack:
a hosted model cannot have a higher version than the server model: 2.3.3 > 2.3.2
github.com/juju/juju/rpc/client.go:149:
github.com/juju/juju/api/apiclient.go:924:
I am a little baffled at what the problem might be. This controller has no vm
associated with it.
--
Daniel Bidwell
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
redhat, centos, oracle linux images for vmware deployment
Where do I find the images that are used by juju to deploy to a vsphere controller? My ubuntu systems come up great, but unfortunately I need to deploy some red hat/centos/oracle linux vms also, but juju deploy doesn't seem to be able to find them. Is this an area that needs someone to get involved with? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju deploys with a vsphere controller using hardware vm version 10
Yes, that would be great! I am sure that 14 will become available soon with a patch to vmware. We are vmware version 6.5 which only presents us with version 13. There are supposed to be some significant performance improvements between 10 and 13. On Wed, 2018-02-07 at 12:24 +1000, Ian Booth wrote: > Hi Daniel > > The Juju vSphere provider currently only supports hardware version > 10, but 14 is > now the most recent according to the VMWare website. If we were > simply to track > and support the most recent hardware version, would that work for > you? > > On 05/02/18 12:38, Daniel Bidwell wrote: > > > > Is there anyway to make the vsphere controller to deploy vms with > > hardware vm version 13 instead of version 10? > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju deploys with a vsphere controller using hardware vm version 10
Is there anyway to make the vsphere controller to deploy vms with hardware vm version 13 instead of version 10? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju juju-upgrade -m controller woes
I have a vmware vm on my public network that is my juju host. In it I have an lxc container that is also bridged to my public network. I bootstrapped it with: juju bootstrap manual/ipaddress modelname I also created vms with public IP addresses that I setup an ubuntu account and added as: juju add-machine ssh:ubuntu@ipaddress all machines have public ip address and full routing. The controller container was running juju version 2.2.6 (unsupported) while the main machine had been upgraded to 2.3.2. juju status produces: ModelController Cloud/Region Version SLA default uncloud manual2.2.6unsupported App Version Status Scale Charm Store Rev OS Notes au-webcluster-member active 1 au-webcluster-member local0 ubuntu aubase1active 1 aubase1 local0 ubuntu Unit Workload Agent Machine Public address Ports Message au-webcluster-member/0* activeidle 1webc4 Web cluster member for instance test completed aubase1/0* activeidle 1webc4 Machine StateDNS Inst id Series AZ Message 0down amzsend manual:amzsend xenial Manually provisioned machine 1started webc4manual:webc4xenial Manually provisioned machine 2pending webc5manual:webc5xenial Manually provisioned machine machine 2 failed to "add". The upgrade-juju command now says: ERROR some agents have not upgraded to the current model version 2.2.6: machine-2 but juju doesn't let me do anything with machine-2 until it is finished with it. I suspect that my only option is to build a new container/controller and redeploy my machines on it before removing the old container/controller. On Tue, 2018-01-30 at 14:40 +0400, John Meinel wrote: > I'm a bit curious what you mean by "manually provisioned machine". > Are you saying that you used the VMWare APIs directly to launch an > instance, and then "juju bootstrap IP" to start using that machine, > and then "juju add-machine ssh:IP" to add the second machine? > > You could try doing "juju upgrade-juju --debug" to see what at least > the client thinks it is trying to do. I wonder if it is a case where > your VM doesn't actually have egress access, but your client does. > And so Jujud on the VM is trying to do something like download the > new agent, which your client saw and said was available, but the > controller isn't actually able to download. > > John > =:-> > > > On Fri, Jan 26, 2018 at 8:48 PM, Daniel Bidwell > wrote: > > I have a juju controller, uncloud, in a container in a vmware vm. > > The > > controller has a manually provisioned machine deployed happily. I > > tried to manually provision a second machine. It is stuck in > > pending > > with no progress after a day of waiting. I can ssh to ubuntu@host > > just > > fine with the ssh keys installed. > > > > I am provisioning from a machine with juju 2.3.2 and the controller > > has > > version 2.2.6 on it (now unsupported). I have attempted to do > > "juju > > upgrade-juju -m uncloud" and it happily says that it is upgrading > > to > > 2.3.2, but I never see any progress with that either (after hours > > or > > days). > > > > What is the secret sauce for making these thing work? For some > > reason, > > whenever I have trouble with my juju environment, I have to destory > > it > > and set up the controllers from scrap. I guess I just don't have > > the > > juju for juju :-( I do like being able to develop charms for my > > apps > > and deploy them though. > > -- > > Daniel Bidwell > > > > > > -- > > Juju-dev mailing list > > juju-...@lists.ubuntu.com > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman > > /listinfo/juju-dev > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju juju-upgrade -m controller woes
I have a juju controller, uncloud, in a container in a vmware vm. The controller has a manually provisioned machine deployed happily. I tried to manually provision a second machine. It is stuck in pending with no progress after a day of waiting. I can ssh to ubuntu@host just fine with the ssh keys installed. I am provisioning from a machine with juju 2.3.2 and the controller has version 2.2.6 on it (now unsupported). I have attempted to do "juju upgrade-juju -m uncloud" and it happily says that it is upgrading to 2.3.2, but I never see any progress with that either (after hours or days). What is the secret sauce for making these thing work? For some reason, whenever I have trouble with my juju environment, I have to destory it and set up the controllers from scrap. I guess I just don't have the juju for juju :-( I do like being able to develop charms for my apps and deploy them though. -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju enable-ha with lxd servers
I have 3 lxd servers, lxd0,lxd1, and lxd2. I did a "juju bootstrap lxd lxd-prod" on lxd0. Now I would like to enable juju high availability with machines lxd1 and lxd2 as secondary juju controllers. I see that I want something like "juju enable-ha -n 3 -server lxd1 lxd2". What form do I need lxd1 and lxd2 in to do this? I tried doing "juju add-machine ssh:root@lxd1" -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju deploy with a series
I am trying to deploy a charm that I am writing for both ubuntu and centos. "lxc image alias list" produces: lxc image alias list +---+--+---+ | ALIAS | FINGERPRINT |DESCRIPTION| +---+--+---+ | centos7 | 41c7bb494bbd | centos7 | +---+--+---+ | juju/xenial/amd64 | 1e59027d1d58 | juju/xenial/amd64 | +---+--+---+ | ubuntu-xenial | 1e59027d1d58 | ubuntu-xenial | +---+--+---+ "juju deploy ~/charms/xenial/aubase1 --series centos7 aubasecentos" looks like it is starting, but a "juju status" produces: juju status ModelController Cloud/Region Version default lxd-testlocalhost/localhost 2.1.2 App Version Status Scale CharmStore Rev OS Notes aubase1active 1 aubase1 local5 ubuntu aubasecentos waiting0/1 aubase1 local4 centos UnitWorkload Agent Machine Public address Ports Message aubase1/4* activeidle910.130.54.192 aubasecentos/4 waiting allocating 10 waiting for machine Machine StateDNSInst idSeries AZ 9started 10.130.54.192 juju-a0c4c9-9 xenial 10 downpendingcentos7 What do I need to do to deploy a centos lxd container with my charm? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
killing old dead controllers
I have a machine with 2 dead controllers that I can't figure out how to delete. A "juju controllers" produces the following: root@juju:~# juju controllers Use --refresh flag with this command to see the latest information. Controller ModelUser Access Cloud/Region Models Machines HA Version lxd-test-admin superuser lxd/localhost 2 1 none 2.0.2 test-lxd* default admin superuser localhost/localhost 2 1 none 2.1.3 lxc list produces: root@juju:~# lxc list +--+---+--+--+--+---+ | NAME | STATE | IPV4 | IPV6 | TYPE | SNAPSHOTS | +--+---+--+--+--+---+ Any attemtp to remove, delete, kill, or destroy results in the command hanging and never coming back. I have been trying to develop some local charms using lxd. I know that this kind of testing and developemnt is hard on vms/containers, but throwing away the vm and reinstalling ubuntu is probably not the desired behaviour. -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Best practice in giving lxd containers routable IP addresses
What is the best practice in giving lxd containers routable IP addresses? I would like to treat the containers as regular vm's for production, not as non-routable devops machines. Is there a document somewhere show how to configure this? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: How to add openstack cloud to juju 2.1.2-xenial
Still facing issues, but have gotten past the simplestreams issue, I
think.
I am running "juju bootstrap acauits --metadata-source
/home/bidwell/simplestreams --debug"
Among everything else, it returns:
caused by: request (http://10.20.9.142:8774/v2.1/e69c1091bf744509a8853e
a8e336ae26/servers) returned unexpected status: 409; error info:
{"conflictingRequest": {"message": "Multiple possible networks found,
use a Network ID to be more specific.", "code": 409}}}])
nova net-list
+--+--+--+
| ID | Label| CIDR |
+--+--+--+
| 0395dae1-1e5e-47cd-bd0f-c058087e292c | maasnet | None |
| 42c432e8-3958-47b2-b84c-df4f0aa0fbe8 | ext_net | None |
| 54ecafdf-acec-44f7-9d78-3c9fdeff5807 | internal | None |
+--+--+--+
neutron subnet-list
+-+-++-+
| id | name| cidr | allocation_pools|
+-+-++-+
| 7818b78f-07bc-4518 | ext_net_subnet | 143.207.0.0/22 | {"start": |
| -838d-0cecb178ffa8 | || "143.207.3.10", |
| | || "end": |
| | || "143.207.3.254"}|
| 9c961866-7c94-4c53- | maassnet| 10.20.8.0/23 | {"start": |
| 96e5-55b328719e97 | || "10.20.8.1", "end": |
| | || "10.20.8.1"}|
| | || {"start": |
| | || "10.20.8.3", "end": |
| | || "10.20.9.254"} |
| ced5bfb0-6bb6-41f8 | internal_subnet | 10.5.5.0/24| {"start": |
| -b98a-bd9bf3b4003e | || "10.5.5.2", "end": |
| | || "10.5.5.254"} |
+-+-++-+
When I start a vm from the dashboard it lands on the internet_subnet.
How do I tell "juju bootstrap" which network to use?
On Tue, 2017-04-18 at 00:15 +0500, Junaid Ali wrote:
> Hi Daniel,
> are you still facing the issue? I was able to give to try this today
> but I couldn't reproduce your issue. I think your issue might be due
> to image id in ~/simplestreams/images/streams/v1/ index.json>. Ensure you have correct image id by comparing it with
> the specific image in $openstack image list.
>
> You can also check if there is any issue on the nova-compute side
> (instance might be failing due to any nova issue causing bootstrap to
> fail).
>
>
> --
> Junaid
>
>
--
Daniel Bidwell
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
Re: How to add openstack cloud to juju 2.1.2-xenial
xd4, 0x48, 0x42, 0x12, 0xdc, 0x5d, 0x76, 0xf6, 0xfb, 0x34, 0xeb, 0xe6,
0x8d, 0x4, 0x0, 0x98, 0xd5, 0xba, 0x1a, 0x7e, 0x8a, 0x1c, 0x23, 0xc2,
0x9b, 0xde, 0xfc, 0x9f, 0xce, 0xec, 0xd4, 0x7d, 0x5f, 0x29, 0x37, 0xd6,
0xf6, 0x72, 0x66, 0xed, 0x37, 0x4b, 0x5e, 0x64, 0xec, 0x10, 0xeb, 0x27,
0xdd, 0x33, 0xd4, 0xc5, 0x7c, 0x7a, 0x1a, 0x19, 0x55, 0x6c, 0xc7, 0xe3,
0x8e, 0x75, 0xd2, 0x12, 0xb9, 0xe0, 0x4a, 0xac, 0x8e, 0x35, 0x45, 0x89,
0x77, 0x36, 0x33, 0x16, 0xc1, 0x2c, 0xc1, 0xfc, 0x8c, 0xa0, 0xc6, 0xed,
0x9d, 0x78, 0x8a, 0x1c, 0x59, 0x6c, 0x97, 0xfd, 0x64, 0x1b, 0x75, 0xe6,
0x24, 0x3f, 0xe3, 0x68, 0x4e, 0x37, 0x99, 0x24, 0x8a, 0x61, 0xcf, 0x39,
0x4f, 0x88, 0x5c, 0xcc, 0x18, 0xba, 0xdc, 0x6, 0x12, 0x74, 0x3b, 0xc1,
0x24, 0xa9, 0xba, 0xf3, 0xcc, 0x34, 0x66, 0x87, 0x7e, 0x41, 0x6e, 0xe1,
0xd2, 0x79, 0x97, 0x93, 0xa4, 0xd8, 0xe3, 0xf3, 0xe5, 0x3d, 0xd8, 0xf4,
0xc8, 0x25, 0xb1, 0xa4, 0x95, 0xec, 0x59, 0x1f, 0xea, 0x29, 0x49, 0xb6,
0xe4, 0xc3, 0x11, 0xab, 0xb7, 0xd5, 0x69, 0xa0, 0xf9, 0x47, 0xfd, 0x60,
0xad, 0xe4, 0xfd, 0x71, 0xdd, 0x8b, 0x2b, 0xc3, 0x8, 0xa7, 0x3a, 0x3f,
0x38, 0xd4, 0xc8, 0x98, 0xb3, 0x96, 0x34, 0x3d, 0x83, 0x1f, 0x96, 0xa2,
0xf6, 0x74, 0x73, 0xba, 0x95, 0xec, 0x6c, 0x64, 0xca, 0xfc, 0x60, 0x29,
0x8a, 0x71, 0x7d, 0xb3, 0xb4, 0x95, 0xd7, 0x27, 0xab, 0x64, 0xb6, 0x1d,
0x5b, 0xd5, 0x65, 0x1f, 0xb9, 0xe9, 0x6, 0xab, 0xd0, 0xea, 0xde, 0xfa,
0xf6, 0x22, 0x5f, 0x75, 0x96, 0xdb, 0xec, 0x76, 0x5b, 0xfb, 0x7a, 0x5b,
0xd3, 0xb2, 0xb6, 0xb1, 0x95, 0x3b, 0x54, 0xb6, 0x93, 0xd8, 0x74, 0xb9,
0x3d, 0x4e, 0xf7, 0x1b, 0xc9, 0x1c, 0xef, 0xaf, 0xf9, 0x71, 0x37, 0xbb,
0xbd, 0x2c, 0x78, 0x6a, 0xc3, 0xdd, 0x7b, 0xe8, 0xbf, 0x54, 0xb5, 0xea,
0x94, 0xe3, 0x9, 0xda, 0xde, 0xa1, 0x4f, 0x77, 0x96, 0x69, 0xd, 0x56,
0xcb, 0x72, 0xb9, 0x1a, 0xa0, 0x9e, 0x77, 0xa4, 0xed, 0xcc, 0x23, 0x7f,
0x76, 0xc6, 0xc5, 0x7e, 0x55, 0x4f, 0xd3, 0xcf, 0xc, 0x66, 0x15, 0xbe,
0x7f, 0x99, 0x9b, 0x89, 0x7c, 0xcc, 0x8e, 0xb6, 0x58, 0xbc, 0xfe, 0x50,
0xff, 0xfd, 0x8, 0x56, 0xeb, 0x8d, 0x66, 0x59, 0x87, 0xc9, 0xb0, 0xde,
0x3d, 0xfd, 0x11, 0x0, 0x0, 0xff, 0xff, 0x6c, 0x3d, 0x94, 0xa3, 0xd8,
0x6, 0x0, 0x0},
SecurityGroupNames:[]nova.SecurityGroupName{nova.SecurityGroupName{Name
:"juju-bb622553-b48c-4c8c-8a2d-5a2e7cd74254-5482ff53-12f0-445b-84f1-
9c9f4a0c7cc8"}, nova.SecurityGroupName{Name:"juju-bb622553-b48c-4c8c-
8a2d-5a2e7cd74254-5482ff53-12f0-445b-84f1-9c9f4a0c7cc8-0"}},
Networks:[]nova.ServerNetworks{}, AvailabilityZone:"nova",
Metadata:map[string]string{"juju-model-uuid":"5482ff53-12f0-445b-84f1-
9c9f4a0c7cc8", "juju-controller-uuid":"bb622553-b48c-4c8c-8a2d-
5a2e7cd74254", "juju-is-controller":"true"}, ConfigDrive:false}
caused by: request (http://10.20.9.142:8774/v2.1/e69c1091bf744509a8853e
a8e336ae26/servers) returned unexpected status: 400; error info:
{"badRequest": {"message": "Invalid input for field/attribute imageRef.
Value: xenial. u'xenial' is not valid under any of the given schemas",
"code": 400}}}])
What happened?
On Thu, 2017-04-13 at 10:23 +0500, Junaid Ali wrote:
> Have you tried using the local meta-data source directory instead of
> using the swift URL
>
> > juju bootstrap acauits --metadata-source=~/simplestreams/images --
> > debug
> Or you can copy the metadata source to juju client machine's
> /var/www/, setup apache and update the image-metadata-url to point to
> your local web server
>
>
> --
> Junaid
>
> On Thu, Apr 13, 2017 at 2:09 AM, Daniel Bidwell
> wrote:
> > OK, I found an index.json at http://10.20.9.139/swift/images/stream
> > s/v1
> > /index.json but it's contents looks like:
> >
> > {"Code":"MethodNotAllowed","RequestId","tx
> > and doesn't look anything like the one that was generated in my
> > ~/simplestreams/images/streams/v1/index.json.
> >
> > I went through the instructions from John Meinel > l.co
> > m> at https://github.com/juju/docs/blob/master/src/en/howto-private
> > clou
> > d.md.
> >
> > Connecting juju to MAAS was a whole lot simpler.
> >
> > Any other ideas?
> >
> > On Wed, 2017-04-12 at 15:25 -0400, Heather Lanigan wrote:
> > > From the log:
> > >
> > > 14:27:33 DEBUG juju.environs.bootstrap bootstrap.go:579 ignoring
> > > image
> > > metadata in image-metadata-url: invalid URL "http://10.20.9.139:8
> > 0/sw
> > > if
> > > t/v1/streams/v1/index.json" not found
> > >
> > > To use the data you collected, the url must work. Try modifying
> > the
> > > URL in the CLI to get to index.json. It looks like the tenant
> > info
> > > is missing from it, maybe something else as well. You should be
> > able
> >
Re: How to add openstack cloud to juju 2.1.2-xenial
OK, I found an index.json at http://10.20.9.139/swift/images/streams/v1
/index.json but it's contents looks like:
{"Code":"MethodNotAllowed","RequestId","tx
and doesn't look anything like the one that was generated in my
~/simplestreams/images/streams/v1/index.json.
I went through the instructions from John Meinel at https://github.com/juju/docs/blob/master/src/en/howto-privateclou
d.md.
Connecting juju to MAAS was a whole lot simpler.
Any other ideas?
On Wed, 2017-04-12 at 15:25 -0400, Heather Lanigan wrote:
> From the log:
>
> 14:27:33 DEBUG juju.environs.bootstrap bootstrap.go:579 ignoring
> image
> metadata in image-metadata-url: invalid URL "http://10.20.9.139:80/sw
> if
> t/v1/streams/v1/index.json" not found
>
> To use the data you collected, the url must work. Try modifying the
> URL in the CLI to get to index.json. It looks like the tenant info
> is missing from it, maybe something else as well. You should be able
> to do a wget on the url constructed to download the index.json
> for verification.
>
> -Heather
>
>
> On Wed, Apr 12, 2017 at 2:32 PM, Daniel Bidwell
> wrote:
> > juju --verbose --debug bootstrap acauits --config image-metadata-
> > url=h
> > ttp://10.20.9.139:80/swift/v1 --config network=42c432e8-3958-47b2-
> > b84c-
> > df4f0aa0fbe8
> >
> > 14:27:31 INFO juju.cmd supercommand.go:63 running juju [2.1.2 gc
> > go1.6.2]
> > 14:27:31 DEBUG juju.cmd supercommand.go:64 args: []string{"juju",
> > "
> > --verbose", "--debug", "bootstrap", "acauits", "--config", "image-
> > metadata-url=http://10.20.9.139:80/swift/v1";, "--config",
> > "network=42c432e8-3958-47b2-b84c-df4f0aa0fbe8"}
> > 14:27:31 INFO cmd cmd.go:141 no credentials found, checking
> > environment
> > 14:27:31 DEBUG juju.cmd.juju.commands bootstrap.go:780
> > authenticating
> > with region "RegionOne" and credential "admin" (openstack region
> > "RegionOne" project "admin" user "admin")
> > 14:27:31 DEBUG juju.cmd.juju.commands bootstrap.go:892 provider
> > attrs:
> > map[use-floating-ip:false use-default-secgroup:false
> > network:42c432e8-
> > 3958-47b2-b84c-df4f0aa0fbe8 external-network:]
> > 14:27:33 INFO cmd cmd.go:141 Adding contents of
> > "/home/bidwell/.local/share/juju/ssh/juju_id_rsa.pub" to
> > authorized-
> > keys
> > 14:27:33 INFO cmd cmd.go:141 Adding contents of
> > "/home/bidwell/.ssh/id_rsa.pub" to authorized-keys
> > 14:27:33 DEBUG juju.cmd.juju.commands bootstrap.go:948 preparing
> > controller with config: map[ssl-hostname-verification:true apt-
> > http-
> > proxy: ignore-machine-addresses:false logging-config: use-default-
> > secgroup:false apt-mirror: default-series:xenial resource-tags:
> > name:controller net-bond-reconfigure-delay:17 image-metadata-
> > url:http:/
> > /10.20.9.139:80/swift/v1 image-stream:released agent-metadata-url:
> > automatically-retry-hooks:true https-proxy: provisioner-harvest-
> > mode:destroyed proxy-ssh:false firewall-mode:instance agent-
> > stream:released http-proxy: type:openstack enable-os-upgrade:true
> > external-network: authorized-keys:ssh-rsa
> > B3NzaC1yc2EDAQABAAABAQDYVqxnI6EUKENu/WSapHYavwZk/Q430CkDerS
> > dqjX
> > 2hQWIpeMsy3FCiMyb3z6eL3bIiKWh8B2I8Hm8gTbKWPQG2495yZmHxcwOi8ECRPapp5
> > 8d48
> > +qYKYYWwRioC07uMe4/SR3lT1zO0kQ3yPiJOBZbnhksgVV+M4Jwl7lxlsKZfgY6PQ3n
> > 7d61
> > Q5IjOwEU2KekwdNTxwIvYGl52Q6I3o8LY2mJqb+OeQggZH8iSL82M5jqDmOT1ni4D9i
> > g2D1
> > s8jkj8O5gYsKGgRFY+nKh6eWtBuFzkkzXs8X4NRXSKE2OkqYf4Tjp/+1T6hUjAIio37
> > IBbV
> > F8h2e2aUxUTGHm1pp juju-client-key
> > ssh-rsa
> > B3NzaC1yc2EDAQABAAABAQDU8V64uPSRxvs+FS3LmsWjEqEcI8LKHqBIwjT
> > jC0S
> > qAk3rt4j8CA44jUTsILfJkitveaAtTU/qhY3/+u6kRh0KnpvihKoPm2//g5YvDn3rJs
> > exz7
> > 2ab0fDkw1KmQIJW6rnzgMYG3kkrVivxGfP5nxkS2N3cSX8qkkRnXY/wFNq7AdZEWSN3
> > VZO5
> > jwIIgHEtWYoImsYO2AEmaXS485EQHR2TmBQ3tWS44IyFSANc6nNkJRCSwxVhblPi8aS
> > 1z6T
> > LpN0MRmzzOdE+AAm+IR30o3TkjQbtTClVP2QCVypZUJz9LtlTaUGgd9wyZm4ZqaTcW6
> > oUSQ
> > S7NMuMN7e5cZo+mcn bidwell@samwise
> > network:42c432e8-3958-47b2-b84c-df4f0aa0fbe8 enable-os-refresh-
> > update:true apt-https-proxy: use-floating-ip:false uuid:e9dee81e-
> > 7bd8-
> > 4e5f-897a-3427dfc95d41 logforward-enabled:false ftp-proxy: disable-
> > network-management:false development:false apt-ftp-proxy: no-proxy:
> > test-mode:false transmit-vendor-me
Re: How to add openstack cloud to juju 2.1.2-xenial
60,
0xad, 0xe4, 0xfd, 0x71, 0xdd, 0x8b, 0x2b, 0xc3, 0x8, 0xa7, 0x3a, 0x3f,
0x38, 0xd4, 0xc8, 0x98, 0xb3, 0x96, 0x34, 0x3d, 0x83, 0x1f, 0x96, 0xa2,
0xf6, 0x74, 0x73, 0xba, 0x95, 0xec, 0x6c, 0x64, 0xca, 0xfc, 0x60, 0x29,
0x8a, 0x71, 0x7d, 0xb3, 0xb4, 0x95, 0xd7, 0x27, 0xab, 0x64, 0xb6, 0x1d,
0x5b, 0xd5, 0x65, 0x1f, 0xb9, 0xe9, 0x6, 0xab, 0xd0, 0xea, 0xde, 0xfa,
0xf6, 0x22, 0x5f, 0x75, 0x96, 0xdb, 0xec, 0x76, 0x5b, 0xfb, 0x7a, 0x5b,
0xd3, 0xb2, 0xb6, 0xb1, 0x95, 0x3b, 0x54, 0xb6, 0x93, 0xd8, 0x74, 0xb9,
0x3d, 0x4e, 0xf7, 0x1b, 0xc9, 0x1c, 0xef, 0xaf, 0xf9, 0x71, 0x37, 0xbb,
0xbd, 0x2c, 0x78, 0x6a, 0xc3, 0xdd, 0x7b, 0xe8, 0xbf, 0x54, 0xb5, 0xea,
0x94, 0xe3, 0x9, 0xda, 0xde, 0xa1, 0x4f, 0x77, 0x96, 0x69, 0xd, 0x56,
0xcb, 0x72, 0xb9, 0x1a, 0xa0, 0x9e, 0x77, 0xa4, 0xed, 0xcc, 0x23, 0x7f,
0x76, 0xc6, 0xc5, 0x7e, 0x55, 0x4f, 0xd3, 0xcf, 0xc, 0x66, 0x15, 0xbe,
0x7f, 0x99, 0x9b, 0x89, 0x7c, 0xcc, 0x8e, 0xb6, 0x58, 0xbc, 0xfe, 0x50,
0xff, 0xfd, 0x8, 0x56, 0xeb, 0x8d, 0x66, 0x59, 0x87, 0xc9, 0xb0, 0xde,
0x3d, 0xfd, 0x11, 0x0, 0x0, 0xff, 0xff, 0x6c, 0x3d, 0x94, 0xa3, 0xd8,
0x6, 0x0, 0x0},
SecurityGroupNames:[]nova.SecurityGroupName{nova.SecurityGroupName{Name
:"juju-c22bcd7a-1e2a-4081-8a89-1b6781ed2db7-e9dee81e-7bd8-4e5f-897a-
3427dfc95d41"}, nova.SecurityGroupName{Name:"juju-c22bcd7a-1e2a-4081-
8a89-1b6781ed2db7-e9dee81e-7bd8-4e5f-897a-3427dfc95d41-0"}},
Networks:[]nova.ServerNetworks{nova.ServerNetworks{NetworkId:"42c432e8-
3958-47b2-b84c-df4f0aa0fbe8", FixedIp:"", PortId:""}},
AvailabilityZone:"nova", Metadata:map[string]string{"juju-model-
uuid":"e9dee81e-7bd8-4e5f-897a-3427dfc95d41", "juju-controller-
uuid":"c22bcd7a-1e2a-4081-8a89-1b6781ed2db7", "juju-is-
controller":"true"}, ConfigDrive:false}
caused by: request (http://10.20.9.142:8774/v2.1/e69c1091bf744509a8853e
a8e336ae26/servers) returned unexpected status: 400; error info:
{"badRequest": {"message": "Invalid input for field/attribute imageRef.
Value: xenial. u'xenial' is not valid under any of the given schemas",
"code": 400}}}])
On Wed, 2017-04-12 at 23:20 +0500, Junaid Ali wrote:
> Hi Daniel,
> Can you run juju bootstrap command with --debug flag? It should
> provide a more detailed output.
>
>
> --
> Junaid
>
> On Wed, Apr 12, 2017 at 10:23 PM, Daniel Bidwell > wrote:
> > I have followed the new howto-privatecloud down to the juju
> > boostrap
> > command of:
> >
> > juju bootstrap acauits --config image-metadata-url=http://10.20.9.1
> > 39:8
> > 0/swift/v1
> >
> > and it returns:
> >
> > See above.
> >
> > Saying that it can't find my kernel image. However
> >
> > openstack image list
> >
> > returns:
> >
> > +--+++
> > | ID | Name | Status |
> > +--+++
> > | 2785dea7-6d2d-45d4-9d60-37459c008c91 | xenial | active |
> > | 21197538-79c5-4f1f-8487-1f7f367dfc0b | trusty | active |
> > +--+++
> >
> > From the horizon web dashboard I can start a vm with the zenial
> > image.
> > Where do I go next?
> >
> > On Wed, 2017-04-12 at 10:04 +0400, John Meinel wrote:
> > > So while tools would need to be 'agent' it actually needs to be
> > > 'image-metadata-url' for what you are doing, and it looks like
> > the
> > > docs are already updated just waiting to be published into HTML:
> > > https://github.com/juju/docs/blob/master/src/en/howto-privateclo
> > ud.m
> > > d
> > >
> > > John
> > > =:->
> > >
> > >
> > > On Wed, Apr 12, 2017 at 9:56 AM, John Meinel > com>
> > > wrote:
> > > > It sounds like the docs are out of date. The key should be
> > "agent-
> > > > metadata-url" 'tools' was a much older name.
> > > >
> > > > John
> > > > =:->
> > > >
> > > >
> > > > On Wed, Apr 12, 2017 at 7:32 AM, Daniel Bidwell > l.co
> > > > m> wrote:
> > > > > This gets me down to:
> > > > >
> > > > > juju bootstrap acauits acauits-controller --config tools-
> > > > > metadata-url=h
> > > > > ttp://10.20.9.139:80/swift/v1
> > > > >
> > > > > where it gives me:
> > > > >
> > > > > WARNING unknown config field "tools-metadata-url"
> > > > > Creat
Re: How to add openstack cloud to juju 2.1.2-xenial
0xc1, 0xca, 0xe4, 0x5, 0x87, 0xd2, 0xa4, 0xcb, 0xd4, 0x38, 0x89, 0xd5,
0x75, 0x2f, 0x74, 0xd8, 0xfc, 0x3d, 0xdc, 0xbe, 0x39, 0x6d, 0x32, 0x8f,
0xfa, 0xe8, 0xc0, 0x47, 0xe5, 0xdb, 0x2d, 0x49, 0x6e, 0x1f, 0x4c, 0xfd,
0x50, 0x56, 0xdb, 0xf, 0x6b, 0xae, 0x4b, 0xeb, 0xe4, 0xe4, 0x4, 0x8a,
0x1d, 0xe7, 0x62, 0xbb, 0x6b, 0xf7, 0xa3, 0x5d, 0xac, 0x19, 0x98, 0xca,
0x3, 0x63, 0xe4, 0xee, 0xdf, 0xd4, 0x48, 0x42, 0x12, 0xdc, 0x5d, 0x76,
0xf6, 0xfb, 0x34, 0xeb, 0xe6, 0x8d, 0x4, 0x0, 0x98, 0xd5, 0xba, 0x1a,
0x7e, 0x8a, 0x1c, 0x23, 0xc2, 0x9b, 0xde, 0xfc, 0x9f, 0xce, 0xec, 0xd4,
0x7d, 0x5f, 0x29, 0x37, 0xd6, 0xf6, 0x72, 0x66, 0xed, 0x37, 0x4b, 0x5e,
0x64, 0xec, 0x10, 0xeb, 0x27, 0xdd, 0x33, 0xd4, 0xc5, 0x7c, 0x7a, 0x1a,
0x19, 0x55, 0x6c, 0xc7, 0xe3, 0x8e, 0x75, 0xd2, 0x12, 0xb9, 0xe0, 0x4a,
0xac, 0x8e, 0x35, 0x45, 0x89, 0x77, 0x36, 0x33, 0x16, 0xc1, 0x2c, 0xc1,
0xfc, 0x8c, 0xa0, 0xc6, 0xed, 0x9d, 0x78, 0x8a, 0x1c, 0x59, 0x6c, 0x97,
0xfd, 0x64, 0x1b, 0x75, 0xe6, 0x24, 0x3f, 0xe3, 0x68, 0x4e, 0x37, 0x99,
0x24, 0x8a, 0x61, 0xcf, 0x39, 0x4f, 0x88, 0x5c, 0xcc, 0x18, 0xba, 0xdc,
0x6, 0x12, 0x74, 0x3b, 0xc1, 0x24, 0xa9, 0xba, 0xf3, 0xcc, 0x34, 0x66,
0x87, 0x7e, 0x41, 0x6e, 0xe1, 0xd2, 0x79, 0x97, 0x93, 0xa4, 0xd8, 0xe3,
0xf3, 0xe5, 0x3d, 0xd8, 0xf4, 0xc8, 0x25, 0xb1, 0xa4, 0x95, 0xec, 0x59,
0x1f, 0xea, 0x29, 0x49, 0xb6, 0xe4, 0xc3, 0x11, 0xab, 0xb7, 0xd5, 0x69,
0xa0, 0xf9, 0x47, 0xfd, 0x60, 0xad, 0xe4, 0xfd, 0x71, 0xdd, 0x8b, 0x2b,
0xc3, 0x8, 0xa7, 0x3a, 0x3f, 0x38, 0xd4, 0xc8, 0x98, 0xb3, 0x96, 0x34,
0x3d, 0x83, 0x1f, 0x96, 0xa2, 0xf6, 0x74, 0x73, 0xba, 0x95, 0xec, 0x6c,
0x64, 0xca, 0xfc, 0x60, 0x29, 0x8a, 0x71, 0x7d, 0xb3, 0xb4, 0x95, 0xd7,
0x27, 0xab, 0x64, 0xb6, 0x1d, 0x5b, 0xd5, 0x65, 0x1f, 0xb9, 0xe9, 0x6,
0xab, 0xd0, 0xea, 0xde, 0xfa, 0xf6, 0x22, 0x5f, 0x75, 0x96, 0xdb, 0xec,
0x76, 0x5b, 0xfb, 0x7a, 0x5b, 0xd3, 0xb2, 0xb6, 0xb1, 0x95, 0x3b, 0x54,
0xb6, 0x93, 0xd8, 0x74, 0xb9, 0x3d, 0x4e, 0xf7, 0x1b, 0xc9, 0x1c, 0xef,
0xaf, 0xf9, 0x71, 0x37, 0xbb, 0xbd, 0x2c, 0x78, 0x6a, 0xc3, 0xdd, 0x7b,
0xe8, 0xbf, 0x54, 0xb5, 0xea, 0x94, 0xe3, 0x9, 0xda, 0xde, 0xa1, 0x4f,
0x77, 0x96, 0x69, 0xd, 0x56, 0xcb, 0x72, 0xb9, 0x1a, 0xa0, 0x9e, 0x77,
0xa4, 0xed, 0xcc, 0x23, 0x7f, 0x76, 0xc6, 0xc5, 0x7e, 0x55, 0x4f, 0xd3,
0xcf, 0xc, 0x66, 0x15, 0xbe, 0x7f, 0x99, 0x9b, 0x89, 0x7c, 0xcc, 0x8e,
0xb6, 0x58, 0xbc, 0xfe, 0x50, 0xff, 0xfd, 0x8, 0x56, 0xeb, 0x8d, 0x66,
0x59, 0x87, 0xc9, 0xb0, 0xde, 0x3d, 0xfd, 0x11, 0x0, 0x0, 0xff, 0xff,
0x6c, 0x3d, 0x94, 0xa3, 0xd8, 0x6, 0x0, 0x0},
SecurityGroupNames:[]nova.SecurityGroupName{nova.SecurityGroupName{Name
:"juju-1a3bfd40-7d3d-4b1e-8a29-a2730c615844-b9fc698b-c735-41c0-8e39-
dfbdd78344e6"}, nova.SecurityGroupName{Name:"juju-1a3bfd40-7d3d-4b1e-
8a29-a2730c615844-b9fc698b-c735-41c0-8e39-dfbdd78344e6-0"}},
Networks:[]nova.ServerNetworks{}, AvailabilityZone:"nova",
Metadata:map[string]string{"juju-model-uuid":"b9fc698b-c735-41c0-8e39-
dfbdd78344e6", "juju-controller-uuid":"1a3bfd40-7d3d-4b1e-8a29-
a2730c615844", "juju-is-controller":"true"}, ConfigDrive:false}
caused by: request (http://10.20.9.142:8774/v2.1/e69c1091bf744509a8853e
a8e336ae26/servers) returned unexpected status: 400; error info:
{"badRequest": {"message": "Invalid input for field/attribute imageRef.
Value: xenial. u'xenial' is not valid under any of the given schemas",
"code": 400}}
Saying that it can't find my kernel image. However
openstack image list
returns:
+--+++
| ID | Name | Status |
+--+++
| 2785dea7-6d2d-45d4-9d60-37459c008c91 | xenial | active |
| 21197538-79c5-4f1f-8487-1f7f367dfc0b | trusty | active |
+--+++
From the horizon web dashboard I can start a vm with the zenial image.
Where do I go next?
On Wed, 2017-04-12 at 10:04 +0400, John Meinel wrote:
> So while tools would need to be 'agent' it actually needs to be
> 'image-metadata-url' for what you are doing, and it looks like the
> docs are already updated just waiting to be published into HTML:
> https://github.com/juju/docs/blob/master/src/en/howto-privatecloud.m
> d
>
> John
> =:->
>
>
> On Wed, Apr 12, 2017 at 9:56 AM, John Meinel
> wrote:
> > It sounds like the docs are out of date. The key should be "agent-
> > metadata-url" 'tools' was a much older name.
> >
> > John
> > =:->
> >
> >
> > On Wed, Apr 12, 2017 at 7:32 AM, Daniel Bidwell > m> wrote:
> > > This gets me down to:
> > >
> > > juju bootstrap acauits acauits-controller --config tools-
> > > metadata-url=h
> > > ttp://10.20.9.139:80/swift/v1
> > >
> > > where it gives m
Re: How to add openstack cloud to juju 2.1.2-xenial
This gets me down to: juju bootstrap acauits acauits-controller --config tools-metadata-url=h ttp://10.20.9.139:80/swift/v1 where it gives me: WARNING unknown config field "tools-metadata-url" Creating Juju controller "acauits-controller" on acauits/RegionOne ERROR failed to bootstrap model: no image metadata found I am running juju 2.1.2-xenial-amd64 On Tue, 2017-04-11 at 22:26 -0400, Heather Lanigan wrote: > Here is a link on generating the image metadata: https://jujucharms.c > om/docs/stable/howto-privatecloud > > -Heather > > > On Apr 11, 2017, at 10:20 PM, Daniel Bidwell > > wrote: > > > > I am making progress. My openstack cloud has been added now. > > > > When I do "juju bootstrap acauits" it comes back with: > > > > Creating Juju controller "acauits-RegionOne" on acauits/RegionOne > > ERROR failed to bootstrap model: no image metadata found > > > > How do I get/generate image metadata? > > > > I tried "juju metadata generate-tools", but "juju metadata > > generate- > > image" complains that the controller isn't ready yet. > > > > On Tue, 2017-04-11 at 13:27 -0500, Matthew Helmke wrote: > > > I have an OpenStack deployment. In my novarc file, I have this > > > line: > > > export OS_AUTH_URL=http://FAKEURLFORTHISEMAIL.com:5000/v2.0 > > > > > > Look for a similar line in your novarc. > > > > > > On Tue, Apr 11, 2017 at 1:22 PM, Daniel Bidwell > > com> > > > wrote: > > > > juju add-cloud asks: > > > > > > > > Enter the API endpoint url for the cloud: > > > > https://openstack.example.com:35574/v3.0/ > > > > > > > > What openstack service is it asking for? Is it asking for the > > > > dashboard, nova, or what? > > > > > > > > If I have only one region now, do I give it the same url for > > > > both > > > > the > > > > cloud and region? > > > > > > > > My cloud is up and I can create vm's with the dashboard. I > > > > just > > > > want > > > > to tie it to juju now. > > > > > > > > Thanks. > > > > > > > > On Tue, 2017-04-11 at 06:28 -0500, Matthew Helmke wrote: > > > > > The Juju documentation includes a page dedicated to your > > > > > task. > > > > Here > > > > > is the link: https://jujucharms.com/docs/stable/help-openstac > > > > > k. > > > > > > > > > > The tl;dr for your specific question is that if you want to > > > > > use > > > > the > > > > > authentication from your existing OpenStack cloud, then > > > > > during > > > > `juju > > > > > add-cloud` you choose the `userpass` auth type and enter the > > > > > URL > > > > for > > > > > the API. This is typically found in your existing novarc > > > > > file. > > > > Follow > > > > > that by running `juju autoload-credentials` and you will be > > > > > all > > > > set. > > > > > > > > > > On Mon, Apr 10, 2017 at 4:11 PM, Daniel Bidwell > > > > ail. > > > > com> > > > > > wrote: > > > > > > I need to add openstack as a cloud to juju 2.1.2-xenial. I > > > > don't > > > > > > seem > > > > > > to find the right howto. What authentication method do I > > > > > > use? > > > > And > > > > > > where do I get the authentication string? User name and > > > > password > > > > > > for > > > > > > dashboard user? > > > > > > -- > > > > > > Daniel Bidwell > > > > > > > > > > > > > > > > > > -- > > > > > > Juju mailing list > > > > > > Juju@lists.ubuntu.com > > > > > > Modify settings or unsubscribe at: https://lists.ubuntu.com > > > > > > /mai > > > > lman > > > > > > /listinfo/juju > > > > > > > > > > > -- > > > > > Matthew Helmke > > > > > Documentation > > > > > Canonical > > > > -- > > > > Daniel Bidwell > > > > > > > > > > > -- > > > Matthew Helmke > > > Documentation > > > Canonical > > -- > > Daniel Bidwell > > > > > > -- > > Juju mailing list > > Juju@lists.ubuntu.com > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman > > /listinfo/juju -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: How to add openstack cloud to juju 2.1.2-xenial
I am making progress. My openstack cloud has been added now. When I do "juju bootstrap acauits" it comes back with: Creating Juju controller "acauits-RegionOne" on acauits/RegionOne ERROR failed to bootstrap model: no image metadata found How do I get/generate image metadata? I tried "juju metadata generate-tools", but "juju metadata generate- image" complains that the controller isn't ready yet. On Tue, 2017-04-11 at 13:27 -0500, Matthew Helmke wrote: > I have an OpenStack deployment. In my novarc file, I have this line: > export OS_AUTH_URL=http://FAKEURLFORTHISEMAIL.com:5000/v2.0 > > Look for a similar line in your novarc. > > On Tue, Apr 11, 2017 at 1:22 PM, Daniel Bidwell > wrote: > > juju add-cloud asks: > > > > Enter the API endpoint url for the cloud: > > https://openstack.example.com:35574/v3.0/ > > > > What openstack service is it asking for? Is it asking for the > > dashboard, nova, or what? > > > > If I have only one region now, do I give it the same url for both > > the > > cloud and region? > > > > My cloud is up and I can create vm's with the dashboard. I just > > want > > to tie it to juju now. > > > > Thanks. > > > > On Tue, 2017-04-11 at 06:28 -0500, Matthew Helmke wrote: > > > The Juju documentation includes a page dedicated to your task. > > Here > > > is the link: https://jujucharms.com/docs/stable/help-openstack. > > > > > > The tl;dr for your specific question is that if you want to use > > the > > > authentication from your existing OpenStack cloud, then during > > `juju > > > add-cloud` you choose the `userpass` auth type and enter the URL > > for > > > the API. This is typically found in your existing novarc file. > > Follow > > > that by running `juju autoload-credentials` and you will be all > > set. > > > > > > On Mon, Apr 10, 2017 at 4:11 PM, Daniel Bidwell > com> > > > wrote: > > > > I need to add openstack as a cloud to juju 2.1.2-xenial. I > > don't > > > > seem > > > > to find the right howto. What authentication method do I use? > > And > > > > where do I get the authentication string? User name and > > password > > > > for > > > > dashboard user? > > > > -- > > > > Daniel Bidwell > > > > > > > > > > > > -- > > > > Juju mailing list > > > > Juju@lists.ubuntu.com > > > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mai > > lman > > > > /listinfo/juju > > > > > > > > > > > > > -- > > > Matthew Helmke > > > Documentation > > > Canonical > > -- > > Daniel Bidwell > > > > > > > -- > Matthew Helmke > Documentation > Canonical -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: How to add openstack cloud to juju 2.1.2-xenial
juju add-cloud asks: Enter the API endpoint url for the cloud: https://openstack.example.com:35574/v3.0/ What openstack service is it asking for? Is it asking for the dashboard, nova, or what? If I have only one region now, do I give it the same url for both the cloud and region? My cloud is up and I can create vm's with the dashboard. I just want to tie it to juju now. Thanks. On Tue, 2017-04-11 at 06:28 -0500, Matthew Helmke wrote: > The Juju documentation includes a page dedicated to your task. Here > is the link: https://jujucharms.com/docs/stable/help-openstack. > > The tl;dr for your specific question is that if you want to use the > authentication from your existing OpenStack cloud, then during `juju > add-cloud` you choose the `userpass` auth type and enter the URL for > the API. This is typically found in your existing novarc file. Follow > that by running `juju autoload-credentials` and you will be all set. > > On Mon, Apr 10, 2017 at 4:11 PM, Daniel Bidwell > wrote: > > I need to add openstack as a cloud to juju 2.1.2-xenial. I don't > > seem > > to find the right howto. What authentication method do I use? And > > where do I get the authentication string? User name and password > > for > > dashboard user? > > -- > > Daniel Bidwell > > > > > > -- > > Juju mailing list > > Juju@lists.ubuntu.com > > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman > > /listinfo/juju > > > > > -- > Matthew Helmke > Documentation > Canonical -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
How to add openstack cloud to juju 2.1.2-xenial
I need to add openstack as a cloud to juju 2.1.2-xenial. I don't seem to find the right howto. What authentication method do I use? And where do I get the authentication string? User name and password for dashboard user? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
updating ceph-osd config
I started out installing openstack-base and then went back to add more disks to be used for block storage. The default was /dev/sdb. I added /dev/sda, /dev/sdc, and /dev/sdd via the juju gui, saved and deployed. Nothing happened. I just went in and partitioned /dev/sda, /dev/sdc, and /dev/sdd on all machines. Using 2.0.2-xenial-amd64 how do I tell ceph-osd to go reread the configuration and setup the additional disks? There is a resolved/retry in the gui, but these don't have errors and thus there is nothing to resolve/retry. -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: maas grub issue
I forgot the cross-post to maas-devel until after I sent this one and sent it there also. I have some older servers in my test cluster that will only do wakeonlan and not ipmi. I was told that wakeonlan was no longer available in maas 2.0 and was trying to keep my test cluster on the same software as my production cluster. The old servers are HP DL- 180's and they only do wakeonlan and something that I have been lead to believe is proprietary. I would love to be wrong about the wakeonlan and maas 2.0 though. On Thu, 2016-10-06 at 08:22 -0700, Mark Shuttleworth wrote: > 'scuse the cross-post but I think you'll get a faster answer from > maas-devel. I'll start by asking if you've tried MAAS 2.0? > > Mark > > On 06/10/16 08:18, Daniel Bidwell wrote: > > > > I have a maas-1.9.4 with servers with 4 2T disks for data storage > > and a > > 120GB disk on an onboard controller for the system disk. Maas is > > deploying ubuntu 16.04 on the servers. Ubuntu 16.04 labels the > > 120GB > > system disk as /dev/sde, not /dev/sda. In maas I can define the > > /sdev/sde disk as the system disk. > > > > juju bootstrap deploys the system and installs the OS on /dev/sde1 > > but > > fails to write the grub record to /dev/sde and leaves the disk > > unbootable. The system fails over to booting from an ephemeral > > iscsi > > file system where I can examine the state of the machine. > > > > The disk is formated with a GPT partition table which grub will not > > write to unless I manually create a small partition as partition 1 > > with > > blocks from 34-2047 and the system partition as partition 2. > > > > This manual step really not acceptable for deploying from juju and > > maas. > > > > How do I get maas to deploy the system in a way that it will boot > > without manual editing? > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
maas grub issue
I have a maas-1.9.4 with servers with 4 2T disks for data storage and a 120GB disk on an onboard controller for the system disk. Maas is deploying ubuntu 16.04 on the servers. Ubuntu 16.04 labels the 120GB system disk as /dev/sde, not /dev/sda. In maas I can define the /sdev/sde disk as the system disk. juju bootstrap deploys the system and installs the OS on /dev/sde1 but fails to write the grub record to /dev/sde and leaves the disk unbootable. The system fails over to booting from an ephemeral iscsi file system where I can examine the state of the machine. The disk is formated with a GPT partition table which grub will not write to unless I manually create a small partition as partition 1 with blocks from 34-2047 and the system partition as partition 2. This manual step really not acceptable for deploying from juju and maas. How do I get maas to deploy the system in a way that it will boot without manual editing? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju-1.25.6 on xenial not using lxd containers
I have juju-1.25.6 on xenial and am trying to configure it to use the local lxc containers. I have lxd configured to use a zfs volume for containers. My .juju/environment.yaml looks like: local: type: local lxc-clone: true root-dir: /envision/lxc network-bridge: lxdbr0 default-series: trusty lxd is configured correctly to use the zfs storage. When I do the juju bootstrap and deploys, they look like containers but do not show up in "lxc list". They are also stored in /var/lib/... They look like old style lxc containers instead of lxd containers. What do I need to do differently to get juju to use the lxc launch containers? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
1.25.6-xenial-amd64 and lxc containers
What do I have to put in my .juju/environment.yaml to get juju-1.25.6- xenial-amd64 to use lxc containers? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
maas 1.9.4 commissioning fails
I have maas 1.9.4 on trusty. My server has been enlisted, does wake on lan, and commissions. It pxe boots and runs the cloud-init stuff, updates the maas server with its CPUs, memory, and disks, etc, but changes its status to commissioning failed. Where do I find the logs as to why it has failed? I don't see anything helpful on the maas server in /var/log/maas. From watching the console as it runs through everything it looks ok, what I can see as it flies by. Then it powers itself down. -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
maas 1.9.4 and etherwake vs wakeonlan
I have some old servers, HP DL-180's, which wake up with etherwake, but not with wakeonlan or anything else supported by maas. maas 1.7.x supported etherwake, but it appears that maas 1.9.4 does not. Is there any way for me to "reactivate" etherwake for maas 1.9.4? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: maas in a container
Here is my "maastest profile" with lxc profile show maastest name: maastest config: raw.lxc: lxc.cgroup.devices.allow = c 10:237 rwm lxc.cgroup.devices.allow = b 7:* rwm lxc.aa_profile = unconfined security.privileged: "true" description: "" devices: eth0: name: eth0 nictype: bridged parent: br0 type: nic eth1: name: eth1 nictype: bridged parent: br2 type: nic loop0: path: /dev/loop0 type: unix-block loop1: path: /dev/loop1 type: unix-block loop2: path: /dev/loop2 type: unix-block loop3: path: /dev/loop3 type: unix-block loop4: path: /dev/loop4 type: unix-block loop5: path: /dev/loop5 type: unix-block loop6: path: /dev/loop6 type: unix-block loop7: path: /dev/loop7 type: unix-block and container config with lxc config show maastest namname: maastest profiles: - maastest config: volatile.base_image: 8f5108a99312694da883bf1396e688bf9f91cf22061eb9ecd806b43b24c6651f volatile.eth0.hwaddr: 00:16:3e:ee:6f:c4 volatile.eth1.hwaddr: 00:16:3e:ff:9c:be volatile.last_state.idmap: '[]' devices: root: path: / type: disk ephemeral: false It looks like it is giving out dhcp leases correctly, but not mounting the images for the pxeboot tftd. Here is a segment of maastest:/var/log/maas/clusterd.log provisioningserver.utils.shell.ExternalProcessError: Command `sudo /usr/bin/uec2roottar --user=maas /var/lib/maas/boot- resources/cache/root-image- 78c4caf368edf45272fedf7c74b3c29d8a8c74b8e526710f09a1b59488784188 /var/lib/maas/boot-resources/cache/root-tgz- 78c4caf368edf45272fedf7c74b3c29d8a8c74b8e526710f09a1b59488784188` returned non-zero exit status 1: mount: cannot mount block device /dev/loop0 read-only Traceback (most recent call last): File "/usr/bin/uec2roottar", line 27, in uec2roottar.main(args) File "/usr/lib/python2.7/dist- packages/provisioningserver/import_images/uec2roottar.py", line 194, in main extract_image(image, output) File "/usr/lib/python2.7/dist- packages/provisioningserver/import_images/uec2roottar.py", line 177, in extract_image with loop_mount(image, mountpoint): File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/lib/python2.7/dist- packages/provisioningserver/import_images/uec2roottar.py", line 130, in loop_mount check_call(['mount', '-o', 'ro', image, mountpoint]) File "/usr/lib/python2.7/subprocess.py", line 540, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command '[u'mount', u'-o', u'ro', '/var/lib/maas/boot-resources/cache/root-image- 78c4caf368edf45272fedf7c74b3c29d8a8c74b8e526710f09a1b59488784188', u'/tmp/maas-bYv_sD']' returned non-zero exit status 32 The last time I did this it was with maas 1.7 or something like that. I didn't have any trouble with this then. This is with version 1.9.4 on trusty. Would this work better if I just moved it to a physical machine instead of trying to use a container? I don't know which problems are caused by container configuration and which are just some setting tweak of the newer version that I have missed. On Thu, 2016-08-11 at 16:57 -0500, Jason Hobbs wrote: > Daniel, > > Can you show the full dump of your profile and container configs? > > Here's what my 'maas' profile looks like: > > ubuntu@beartic:~$ lxc profile show maas > name: maas > config: > raw.lxc: |- > lxc.cgroup.devices.allow = c 10:237 rwm > lxc.aa_profile = unconfined > lxc.cgroup.devices.allow = b 7:* rwm > security.privileged: "true" > description: "" > devices: > eth0: > name: eth0 > nictype: bridged > parent: br1 > type: nic > loop0: > path: /dev/loop0 > type: unix-block > loop1: > path: /dev/loop1 > type: unix-block > loop2: > path: /dev/loop2 > type: unix-block > loop3: > path: /dev/loop3 > type: unix-block > loop4: > path: /dev/loop4 > type: unix-block > loop5: > path: /dev/loop5 > type: unix-block > loop6: > path: /dev/loop6 > type: unix-block > loop7: > path: /dev/loop7 > type: unix-block > > Here's the config for the container maas is running in: > ubuntu@beartic:~$ lxc config show maas-server > name: maas-server > profiles: > - maas > config: > volatile.base_image: > d23ee1f4fd284aeaba6adeb67cccf7b871e96178d637fec96320aab7cc9634b1 > volatile.eth0.hwaddr: 00:16:3e:ca:9e
Re: maas in a container
I have followed the steps below, but still no luck. Here is what I
have:
/var/log/syslog on my container, maastest, shows:
Aug 10 12:51:05 maastest kernel: [210439.259086] audit: type=1400 audit(14708334
65.435:829): apparmor="DENIED" operation="mount" info="failed flags match" error
=-13 profile="lxd-maastest_" name="/tmp/maas-9bYBDZ/" pid=13267 co
mm="mount" fstype="ext4" srcname="/dev/loop0" flags="ro"
From the machine holding the container a "lxc profile show maastest"
returns:
lxc profile show maastest
name: maastest
config:
raw.lxc: lxc.cgroup.devices.allow = c 10:237 rwm lxc.cgroup.devices.allow = b
7:*
rwm lxc.aa_profile = unconfined
security.privileged: "true"
description: ""
devices:
...
The maastest profile has been applied to the maastest container.
/etc/apparmor.d/lxc-custom-default contains:
profile lxc-container-extx-mounts
flags=(attach_disconnected,mediate_deleted) {
#include
mount fstype=ext4 -> /**,
mount fstype=ext3 -> /**,
mount fstype=ext2 -> /**,
}
Any suggestions as to what I am missing?
On Sat, 2016-08-06 at 22:50 -0500, Jason Hobbs wrote:
> Hi Daniel,
>
> There is some documentation for installing MAAS in a container here:
>
> https://maas.ubuntu.com/docs/install.html#container-install
>
> It's focused on 2.0 but the same steps should work for 1.9.3 too. It
> covers setting up the loop devices.
>
> Hope this helps,
> Jason
>
> On Sat, Aug 6, 2016 at 10:11 PM, Daniel Bidwell
> wrote:
> > I have a lxd container running on 16.04 with maas 1.9.3 running in
> > it.
> >
> > The pxe boot doesn't work because the container doesn't have any
> > /dev/loop* devices and will not allow me to create any.
> >
> > How do I go about creating /dev/loop* devices and allowing them to
> > work
> > in a container?
> > --
> > Daniel Bidwell
> >
> >
> > --
> > Juju mailing list
> > Juju@lists.ubuntu.com
> > Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman
> > /listinfo/juju
> >
--
Daniel Bidwell
--
Juju mailing list
Juju@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju
maas in a container
I have a lxd container running on 16.04 with maas 1.9.3 running in it. The pxe boot doesn't work because the container doesn't have any /dev/loop* devices and will not allow me to create any. How do I go about creating /dev/loop* devices and allowing them to work in a container? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Followup on 16.07 OpenStack charm release
Can I install OpenStack Mitaka on 16.04 with juju-1.25.6 and maas- 1.9.3? Does this support using lxd containers for the OpenStack services? On Mon, 2016-08-01 at 12:02 +, Rick Harding wrote: > You can get juju 1 from the default repositories on xenial with the > package juju-1.25. Right now 1.25.6 is working its way into xenial to > update that. That'll give you a juju-1 command that can live > alongside juju (which is juju 2.0). > > On Mon, Aug 1, 2016 at 4:14 AM Adam Collard om> wrote: > > On Mon, 1 Aug 2016 at 02:43 Daniel Bidwell > > wrote: > > > I am building a pair of maas servers, one for test and one for > > > prod in > > > lxd containers on a single host. The containers are > > > ubuntu/xenial/amd64. Trying to follow David Ames post on Friday > > > to use > > > juju-1.25.6 and maas-1.9.3. What I got from the default > > > repositories > > > was juju 1.25.5 and maas-2.0.0-rc2. While I would like to bring a > > > production OpenStack up on Maas-2.0 and juju-2.0, I don't know if > > > I can > > > wait any longer. > > > > > > What ppa's do I need to use with xenial to get juju-1.25.6 > > https://launchpad.net/~juju/+archive/ubuntu/stable > > > > > and maas-1.9.3? Or does it need to be a trusty server? > > For MAAS 1.9.x, yes, you need a release before Xenial (Trusty being > > the best bet). > > > > https://launchpad.net/~maas/+archive/ubuntu/stable > > > > > -- > > > Daniel Bidwell > > > > > > > > > -- > > > 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 > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Followup on 16.07 OpenStack charm release
I am building a pair of maas servers, one for test and one for prod in lxd containers on a single host. The containers are ubuntu/xenial/amd64. Trying to follow David Ames post on Friday to use juju-1.25.6 and maas-1.9.3. What I got from the default repositories was juju 1.25.5 and maas-2.0.0-rc2. While I would like to bring a production OpenStack up on Maas-2.0 and juju-2.0, I don't know if I can wait any longer. What ppa's do I need to use with xenial to get juju-1.25.6 and maas- 1.9.3? Or does it need to be a trusty server? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju beta upgrade woes
using juju-2.0 beta 9 or 10 I bootstrapped a local/lxd instance and installed wordpress on it. The containers are running. Now juju has upgraded to 2.0 beta 11 and "juju status" returns: ERERROR connecting with bootstrap config: getting API info: model is not bootstrapped juju controllers returns: CONCONTROLLER MODELUSER CLOUD/REGION local.wp* default admin@local Is there a way for me to "get it back" or do I just need to blow it away and start again? Should I be dropping back to juju 1.25.x for this? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Configuring environments.yaml for lxd
I have reinstalled my machine with ubuntu 15.10 to get lxd. I have juju-1.25.0-wily-amd64. lxc image list images: returns a list of images and I have created an lxc container with: lxc launch images:ubuntu/trusty/amd64 lxc-name I have an entry in .juju/environments.yaml that looks like: lxd-local: type: lxd container: lxc default-series: trusty admin-secret: local-lxc juju status returns environment "lxd-local" has an unknown provider type "lxd" What am I still missing? What do I need to do to recognize lxd as a provider? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Neutron networking question with openstack-base
In juju-gui have have the ext-port set to eth3, my public nic. With all networks and routers deleted, "juju get neutron-gatway | grep ext-port" returns "ext-port:", nothing, yet juju-gui still have the correct eth3 value. I add the provider-router and ext_net with: ./neutron-ext-net -g 143.207.94.1 -c 143.207.94.0/24 -f 143.207.94.10:143.207.94.254 ext_net ext_net_subnet says that it is UP and active The port associated with the ext_net_subnet is UP, but the status is down and "juju get neutron-gateway | fgrep ext-port" still returns no nic. juju set neutron-gateway ext-port=eth3 now returns WARNING the configuration setting "ext-port" already has the value "eth3" even though the get doesn't return it and the port is still down. But I can now ping the ext_net interface IP address and the rest of my physical machines that are on the 143.207.94.0/24 network, just not the floating-ip. The internal network has 2 ports, the compute:None which is UP and Active, and the network:router_interface which is UP and Down. This is probably where my problem lies, but I am not sure how to go about fixing it. The provider-router has 2 interfaces, on the ext_net and internal, both have an Admin State of UP, but a status of down. My vm has a floating-ip of 143.207.94.11, but I can't ping it or ssh to it. When the vm boots, but appears to have failed to get an IP address. The ci-info console line says that eth0 is up, but has no address or mask. I don't think I can get into the vm from the console. How do I tell the exact version of OpenStack that I am running? I have Ubuntu 14.04.3 LTS installed and have installed openstack with the openstack-base juju charm. On Mon, 2015-10-19 at 11:10 +0100, Liam Young wrote: > Hi Daniel, > > Have you set 'ext-port' in the neutron-gateway charm? ext-port > specifies the external port the neutron-gateway charm should use for > routing of instance traffic to the external public network. If eth1 on > the neutron-gateway is plumbed into 143.207.94.0/24 network then you > would set it with: > > juju set neutron-gateway ext-port=eth1 > > I'd also take a look at the Network Topology page in the horizon > dashboard and check that ext_net and your private net are both plumbed > into your router and that your instances are plumbed into your private > network. I'm not sure which version of Openstack you are deploying but > certainly in Icehouse I have seen horizon claim the state of > network:router_gateway to be 'down' when it is actually working. > > Do you see the floating IPs that you have assigned your instance(s) > listed when you look at the 'Attached Devices' in the detail tab of > ext_net ? > > Also check that when the instance booted DHCP succeeded. You can do this > through horizon by going to Compute -> Instances -> Click on Instance > Name -> Log tab. The message you are looking for will differ depending > on the image you booted the instance from but something like: > > ci-info: eth0 : 1 192.168.0.4 255.255.255.0 fa:16:3e:ef:d8:53 > > or > > Lease of 192.168.0.2 obtained, lease time 86400 > > Thanks, > Liam Young > > On 15/10/15 20:49, Daniel Bidwell wrote: > > I have installed a small openstack cloud with the openstack-base charm. > > > > After everything came up I ran the neutron-ext-net and > > neutron-tenant-net. I ran neutron-ext-net with -g 143.207.94.1 -c > > 143.207.94.0/24 -f 143.207.94.10:143.207.94.254 ext_net > > > > Each machine in my cloud has an interface on the 143.207.94.0/24 > > network. When I look at the horizon dashboard, under > > admin->networks->ext_net it says that the port on 143.207.94.x as > > network:router_gateway has an admin state of UP, but a Status of Down > > and I have now access from the external addresses on 143.207.94.0 to the > > internal addresses on the 143.207.94.0 network. I have tried to set the > > access rules for ping and ssh, but nothing goes through. > > > > How do I find out why the two different networks don't connect? How do > > I make them connect? > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Neutron networking question with openstack-base
I have installed a small openstack cloud with the openstack-base charm. After everything came up I ran the neutron-ext-net and neutron-tenant-net. I ran neutron-ext-net with -g 143.207.94.1 -c 143.207.94.0/24 -f 143.207.94.10:143.207.94.254 ext_net Each machine in my cloud has an interface on the 143.207.94.0/24 network. When I look at the horizon dashboard, under admin->networks->ext_net it says that the port on 143.207.94.x as network:router_gateway has an admin state of UP, but a Status of Down and I have now access from the external addresses on 143.207.94.0 to the internal addresses on the 143.207.94.0 network. I have tried to set the access rules for ping and ssh, but nothing goes through. How do I find out why the two different networks don't connect? How do I make them connect? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Trying to remove and redeploy quantum-gateway on a different server
; > > > > At this point I managed to get rid of everything — i.e. I do not have > > > > > a > > > > > quantum-gateway or a neutron-gateway as reported by juju. > > > > > > > > > > However, I have noticed that the original server (colocated compute > > > > > and > > > > > quantum-gateway) still has all of the neutron services running. > > > > > Issuing a > > > > > `neutron agent-list` shows everything connected and happy as it ever > > > > > was. > > > > > It seems as though my juju fiddling has basically been just > > > > > manipulating > > > > > the juju database without actually removing the underlying services. > > > > > I have > > > > > noticed that when removing services on an lxc container it does > > > > > indeed kill > > > > > the container (so obviously the service too)… however, maybe because > > > > > this > > > > > original service was deployed on bare metal with another service, it > > > > > doesn’t bother to actually stop the services and remove their > > > > > /etc/init > > > > > files? > > > > > > > > > This does sound unexpected, hopefully someone more directly involved > > > > with > > > > Juju can comment here. > > > > > > > > > > > > > I have tried to redeploy via openstack-status, but it seems like it is > > > > > useless for future deployment even though it has that nice > > > > > curses-looking > > > > > GUI from which I can deploy. It’s understanding of where everything is > > > > > placed is completely broken, and it does not seem to honor any > > > > > requests to > > > > > place stuff in the first place. > > > > > > > > > I'll follow up with you about the openstack-status tool on the installer > > > > list, to keep this thread juju-specific. > > > > > > > > > > > > > Any ideas? > > > > > > > > > > Thanks, > > > > > > > > > > Jeff > > > > > > > > > > -- > > > > > Juju mailing list > > > > > Juju@lists.ubuntu.com > > > > > Modify settings or unsubscribe at: > > > > > https://lists.ubuntu.com/mailman/listinfo/juju > > > > > > > > > > > > > > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: What basic services are you missing in the charm store?
I'll +1 the nginx charm On Mon, 2015-08-24 at 13:01 -0400, Richard Harding wrote: > On Mon, 24 Aug 2015, Jorge O. Castro wrote: > > > Hi everyone, > > > > I'm taking a quick informal survey. We have teams working on things > > like really complicated big data stacks[1] and container orchestration > > awesomeness[2]. > > > > However I wanted to take a minute to ask people what basic, normal, > > boring services they feel are missing from the charm store. Things > > that we tend to forget because we're thinking of the complex problems. > > For example, Robie Basak pointed out to me that it'd be nice to have a > > "mail-in-the-box" style bundle that did a secure, simple mail server > > stack and that it'd be nice to have a promoted "just a blog" bundle > > that is more straightforward. > > > > Things of that sort. > > > > 1: https://jujucharms.com/u/bigdata-dev/realtime-syslog-analytics > > 2: https://github.com/kubernetes/kubernetes/tree/master/cluster/juju/bundles > > > With the recent discussion and focus on things for developers there's a > couple I think that would be cool > > One that I think would be cool is sentry [1][2]. It's a great debugging tool > for python applications and if things like the django framework charm > supported it ootb it'd make an amazing one-two punch for developers. It can > also be used from ruby and other languages. newrelic [3] is another in this > category. I see a charm was created but not tried it out [4] > > The other I think that would be great would be nginx [5]. I know personally > I've used it to replace apache, haproxy, and squid into a single service. > If that were able to work with SSL termination, static file caching, and > proxying scaled up applications behind it, that'd be great for a density > story, good development practices story, etc. > > I sure wish we could package up travisci as that would be awesome to go > with folks code and run your own internally/etc. > > > 1: https://getsentry.com/welcome/ > 2: https://github.com/getsentry/sentry > 3: http://newrelic.com/application-monitoring > 4: https://jujucharms.com/newrelic/precise/3 > 5: https://launchpad.net/ubuntu/+source/nginx > > -- > > Rick Harding > > Juju UI Engineering > https://launchpad.net/~rharding > @mitechie > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: Fwd: How to do network segregation with Juju deployment ?
Does the --networks=... actually bring up the maas nodes? That would be simpler then doing "juju machine add ..." going in and bringing up the interfaces and then doing "juju deploy --to n". On Fri, 2015-08-07 at 18:52 +0300, Dimiter Naydenov wrote: > Hi, > > We're in currently developing more comprehensive networking features > in Juju, so soon you'll be able to configure this with Juju the way > you like it. > > In the meantime, please ignore the --networks argument - it was > implemented partially as a proof of concept and never officially > supported or documented (it's only supported on MAAS and only for > nodes, not LXC containers or KVM instances). > > If you want to get a node from MAAS on given networks, I'd suggest to > add tags on the nodes (e.g. tag "net_public", "net_internal") and then > use --constraints instead: > $ juju deploy keystone --constraints tags=net_internal,^net_public > > Multiple tags can be specified in a comma-delimited list. If you > prefix a tag with "^" it means "not this tag" (i.e. exclude nodes > matching that tag before deciding which node to provision). > > I hope this helps, and stay tuned for the upcoming networking features > in Juju! > > Cheers, > Dimiter Naydenov > > On 7.08.2015 18:16, 曾建銘 wrote: > > Hi all, > > > > I want to deploy OpenStack by Juju with network segregation. I got > > 3 different subnets in my environment, and follow bellow steps to > > config: > > > > 1. Set interfaces information in MAAS clusters tab. 2. Set networks > > information in MAAS networks tab. 3. Edit the network detail and > > set connected interface cards. > > > > I got two screen shots to display my current settings. > > > > > > > > > > Then, I used below commands try to deploy keystone service in LXC > > with multiple networks: $ juju bootstrap $ juju deploy keystone > > --networks=net_public,net_admin,net_internal --config=config.yaml > > --to lxc:0 > > > > But it stuck for a long time with allocating status, so I checked > > the juju debug logs, then I found logs as below: "ERROR > > juju.provisioner provisioner_task.go:630 cannot start instance for > > machine "0/lxc/1": starting lxc containers with networks is not > > supported yet" > > > > Is there anything I missed? Why juju told me "networks is not > > supported yet"? > > > > I have stuck with this problem for several days. If anyone have > > one minute to give me some hints, I will be very appreciate. > > > > Best Regards, Leon > > > > > > > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: requirements for
I, too, am looking for an example command line to put both juju and landscape on the MAAS server, in containers would be nice, but not necessary. On Tue, 2015-03-31 at 19:19 -0500, Ali wrote: > > >> On Fri, 2015-03-27 at 08:22 -0400, Rafael Gonzalez wrote: > >> Hi Stephen, > >> > >> MAAS would be your first node, if configured robustly enough, it can > >> also run Ubuntu Infrastructure services such as Juju and LandScape. > >> The MAAS server should be on bare metal and separate from any of your > >> OpenStack services. > >> > >> > > > > Hi Rafel, > > Can the Juju orchestration node be co-located on the same machine running > MaaS? It sounds like that might be possible from you're statement above, but > if so how is that configured? > > Thanks, > Ali -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: requirements for
On a MAAS server, how do I fire off juju to run in a container on the MAAS server? I haven't seen any examples of this. I would like my juju server and lanscape service to both be running from containers on my juju server and orchestrate resources from the MAAS. Thanks. On Fri, 2015-03-27 at 08:22 -0400, Rafael Gonzalez wrote: > Hi Stephen, > > MAAS would be your first node, if configured robustly enough, it can > also run Ubuntu Infrastructure services such as Juju and LandScape. > The MAAS server should be on bare metal and separate from any of your > OpenStack services. > > > Regards, > > Rafael O. Gonzalez > > Canonical, Solutions Architect > > rgo...@canonical.com > > > > > On Thu, Mar 26, 2015 at 10:08 PM, Stephen > wrote: > Hi, > > What is the hardware requirements for the > maas-region-controller? > > If OpenStack is installed, which machine > should it be? block, object, controller, etc? > > > > Sometimes I cannot explain my problems > well. > > Cheers, > > Stephen > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju > > -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
MAAS deploy failing
Since I haven't been able to find a listserv specifically for MAAS and this listserv is close to the subject and seems to provide good answers... I have a MAAS server that was last installed December 18, 2014 to test building an OpenStack cloud. When I first built it, it would discover, commission, and deploy physical machines just fine. Over time it starts loosing the ability to deploy machines. It will reboot them and pxe boot them with the installer, but something fails in the installer process and they end up in one of 2 states. 1. claim to be deployed, but the machine ends up powered down. The last node event is something like: Failed to query node's BMC — Node could not be queried node-27aac898-bec8-11e4-bb0d-180373b04ac9 (esxi06.maas) connection timeout or 2. fails the deploy, but finishes the install, but never configures the network interfaces and will not talk to the world (thus the failed deploy). The last node event for this one also looks like: Failed to query node's BMC — Node could not be queried node-4881df02-bec8-11e4-bcd7-180373b04ac9 (esxi05.maas) connection timeout I have restarted bind9 (fixed an earlier dns forwarder problem that caused juju to fail in deployments) and maas-dhcp. The machines seem to be getting a correct IP address when booting up, they just don't keep it to the end of their configuration process. I suspect that both problems are related but am not sure where to look to find the debug information on it. Any ideas or suggestions for a better place to ask? I have been having problem with MAAS and juju not being very reliable or stable in repeating operations. Any help is greatly appreciated. -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
Re: juju deploy ceph hangs in pending in maas environment
There is no /var/log/juju on machine-1/unit-ceph-0. I have the cloud-init.log at http://pastebin.com/GKA2W6Cv but am not sure what to look for to figure out why the juju agent was never successfully installed on it? What do I look for? On Thu, 2015-01-29 at 15:59 +, Marco Ceppi wrote: > If you're able to SSH in to the machine, can we see the contents of > `/var/log/juju/unit-ceph-0.log` and `/var/log/juju/machine-1.log` > those will be the first place to look as to why this isn't working. > From the sounds of it, MAAS provisioned the machine but the juju agent > failed to install. The agent-state: pending is a clear indication it > hasn't registered itself with the bootstrap node yet. > > > Thanks, > Marco Ceppi > > On Wed Jan 28 2015 at 4:50:51 PM Daniel Bidwell > wrote: > I have ubuntu 14.04.1 with maas 1.7.1 rc4 and juju 1.20.14. My > client > machine is commissioned and deployed. I can ssh > ubu...@cl1stn2.maas and > I can "juju ssh 1" successfully. I did "juju deploy --config > config.yaml > ceph --to 1". > > juju status ceph looks like: > > juju status ceph > environment: maas > machines: > "1": > agent-state: pending > dns-name: cl1stn2.maas > > instance-id: > /MAAS/api/1.0/nodes/node-caa78cae-a5d5-11e4-b918-180373b04ac9/ > series: trusty > hardware: arch=amd64 cpu-cores=16 mem=24576M > tags=auitsdisk > services: > ceph: > charm: cs:trusty/ceph-31 > exposed: false > relations: > mon: > - ceph > units: > ceph/0: > agent-state: pending > machine: "1" > public-address: cl1stn2.maas > networks: > maas-em1: > provider-id: maas-em1 > cidr: 10.20.0.0/24 > > I don't see any attempt to contact cl1stn2.maas and the status > stays in > pending for ever. I can ssh to cl1stn2.maas and "juju ssh 1" > successfully. I don't see anything in the all-machines.log. > > I can ping from the bootstrap server to the client machine and > from the > client machine to the bootstrap server. They all have proper > dns. > > Where do I look to find out what it is waiting for? > -- > Daniel Bidwell > > > -- > Juju mailing list > Juju@lists.ubuntu.com > Modify settings or unsubscribe at: > https://lists.ubuntu.com/mailman/listinfo/juju -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju deploy ceph hangs in pending in maas environment
I have ubuntu 14.04.1 with maas 1.7.1 rc4 and juju 1.20.14. My client machine is commissioned and deployed. I can ssh ubu...@cl1stn2.maas and I can "juju ssh 1" successfully. I did "juju deploy --config config.yaml ceph --to 1". juju status ceph looks like: juju status ceph environment: maas machines: "1": agent-state: pending dns-name: cl1stn2.maas instance-id: /MAAS/api/1.0/nodes/node-caa78cae-a5d5-11e4-b918-180373b04ac9/ series: trusty hardware: arch=amd64 cpu-cores=16 mem=24576M tags=auitsdisk services: ceph: charm: cs:trusty/ceph-31 exposed: false relations: mon: - ceph units: ceph/0: agent-state: pending machine: "1" public-address: cl1stn2.maas networks: maas-em1: provider-id: maas-em1 cidr: 10.20.0.0/24 I don't see any attempt to contact cl1stn2.maas and the status stays in pending for ever. I can ssh to cl1stn2.maas and "juju ssh 1" successfully. I don't see anything in the all-machines.log. I can ping from the bootstrap server to the client machine and from the client machine to the bootstrap server. They all have proper dns. Where do I look to find out what it is waiting for? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju deploy ceph hangs in pending in maas environment
I have ubuntu 14.04.1 with maas 1.7.1 rc4 and juju 1.20.14. My client machine is commissioned and deployed. I can ssh ubu...@cl1stn2.maas and I can "juju ssh 1" successfully. I did "juju deploy --config config.yaml ceph --to 1". juju status ceph looks like: juju status ceph environment: maas machines: "1": agent-state: pending dns-name: cl1stn2.maas instance-id: /MAAS/api/1.0/nodes/node-caa78cae-a5d5-11e4-b918-180373b04ac9/ series: trusty hardware: arch=amd64 cpu-cores=16 mem=24576M tags=auitsdisk services: ceph: charm: cs:trusty/ceph-31 exposed: false relations: mon: - ceph units: ceph/0: agent-state: pending machine: "1" public-address: cl1stn2.maas networks: maas-em1: provider-id: maas-em1 cidr: 10.20.0.0/24 I don't see any attempt to contact cl1stn2.maas and the status stays in pending for ever. I can ssh to cl1stn2.maas and "juju ssh 1" successfully. I don't see anything in the all-machines.log. I can ping from the bootstrap server to the client machine and from the client machine to the bootstrap server. They all have proper dns. Where do I look to find out what it is waiting for? -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
juju bootstrap finishes but maas deployment fails
I have run "juju -v --debug bootstrap -e auits". The bootstrap appears to have completed. juju says that it is bootstrapped, but the machine is never advanced to the "deployed" state and eventually fails to "Failed deployment". The debug logs can be found at http://pastebin.com/3LDxnQyy Any ideas as to why maas didn't advance the machine to "deployed"? How do I track it down? Thanks. -- Daniel Bidwell -- Juju mailing list Juju@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju
