Hi,

TL;DR:

. novarc
openstack network list

juju bootstrap <cloudname> --config network=<uuid> --config
external-network=<uuid> --config use-floating-ip=true

No need for simplestreams stuff:

Juju deploy this:
https://jujucharms.com/glance-simplestreams-sync/

Then

juju add-relation keystone glance-simplestreams-sync

Note that this uses swift by default so you either need to have radosgw
(which provides swift API) or swift deployed and registered in keystone.

No need to relate glance-simplestreams-sync to anything but keystone - it
will fetch the swift url from keystone.

Might encounter this occasionally:
https://bugs.launchpad.net/juju/+bug/1683495

My mini-guide (just copy-pasted from my stash):
----

https://jujucharms.com/docs/2.1/howto-privatecloud

Remember: for OpenStack you might want to use a private network (specified
by a UUID) but you are not necessarily running from a "bastion" which is on
the same private network. Therefore, you need juju to assign a floating IP
to the controller instance.

# list network uuids
openstack network list

Multiple --config statements can be used instead of a yaml file:
juju bootstrap <cloudname> --config network=<uuid> --config
external-network=<uuid> --config use-floating-ip=true

To check the config parameters available:
juju/provider/openstack/config.go
https://github.com/juju/juju/blob/staging/provider/openstack/config.go#L15

"use-floating-ip": false,
"use-default-secgroup": false,
"network": "",
"external-network": "",

"*use-floating-ip*": {
Description: "Whether a floating IP address is required to give the nodes a
public IP address. Some installations assign public IP addresses by default
without requiring a floating IP address.",
Type: environschema.Tbool,
},
"use-default-secgroup": {
Description: `Whether new machine instances should have the "default"
Openstack security group assigned.`,
Type: environschema.Tbool,
},
"*network*": {
Description: "The network label or *UUID* to bring machines up on when
multiple networks exist.",
Type: environschema.Tstring,
},
"*external-network*": {
Description: "The network label or *UUID* *to create floating IP addresses*
on when multiple external networks exist.",
Type: environschema.Tstring,
},



Best Regards,
Dmitrii Shcherbakov

Field Software Engineer
IRC (freenode): Dmitrii-Sh

On Wed, Apr 26, 2017 at 8:07 PM, Daniel Bidwell <drbidw...@gmail.com> wrote:

> 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/<file-other-than-
> > 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 <drbidw...@gmail.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

Reply via email to