James,
This is fine by me! +1
~James
Hi
>
> We're currently blocked on becoming an OpenStack project under the
> big-tent by the licensing of the 26 OpenStack charms under GPL v3.
>
> I'm proposing that we re-license the following code repositories as Apache
> 2.0:
>
> charm-ceilometer
> c
Hello Team,
I've a few things I want to bring up concerning usability/functionality in
nova-cloud-controller and openstack-dashboard.
1. Request-timeout configurability for openstack-dashboard.
- Everyone who accesses horizon asks me for this. I think it would be
smart to set the timeout to t
I'm having issues with padding when trying to specify key/cert as config
options for Haproxy, and have experienced the same issue in the past, when
trying to specify key/cert for the Openstack charms. Could someone give an
example of what the correct padding of a base64 encoded ssl cert might look
l cert/key
will work for the Openstack charms now that I've got the encoding part
squared away. Still stumped by haproxy though ... can't seem to get it
provision the cert/key correctly for the life of me. Possibly there is
something else I'm missing here ...
On Sat, Jan 28, 2017 at 1:
Trying to bring up an Openstack, I keep hitting this issue where
nova-compute is giving a status "Services not running that should be:
nova-api-metadata" - are others hitting this?
juju status | https://paste.ubuntu.com/26480769/
Its possible something has changed in my infrastructure, but I feel
Hello,
Just wondering if the ceph-radosgw charm provides a method of
configuring/accessing the radosgw-admin utility, or if there is a suggested
way to get radosgw-admin working in conjunction with ceph/ceph-radosgw
charms?
In the ceph-radosgw charm, I see the radosgw-admin bin ends up in
/usr/bi
Concerning the Juju Keystone charm, and api v3, can someone shed some light
on how to find the default admin creds needed to access the keystone api,
or what the novarc file might look like? I'm setting the 'admin-password'
config of the keystone charm to "openstack", and am using this ->
http://pa
I'm having an issue getting a response back (mostly timeouts occur) when
trying to talk to keystone deployed to AWS using private (on vpn) or public
ip address. I've had luck with setting os-*-hostname configs, and ssh'ing
in and running the keystone/openstack client locally from the keystone
insta
Is there a specific reason the barbican charm doesn't have the
os-{internal,private}-hostname config params?
Thanks
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.opens
Another great day of Juju driven successes - deploying the barbican
standalone stack for identity mgmt and secrets mgmt. For those that don't
know, newton horizon brings support for identity only! This means you can
(as I am) use the openstack-dashboard for mgmt of just users, projects, and
domains
Running into a few bumps deploying keystone charm with SSL [1].
I'm wondering how others feel about having the Openstack charms account for
a heightened level of security by opting to use SSL endpoints over plain
http endpoints by default?
Something tells me having services default to using SSL e
11 matches
Mail list logo
