Hi Eren,
I'm pretty sure NECTaR is doing diff versions at different sites in a
widely distributed way.
https://www.openstack.org/user-stories/nectar/
I've cc'd Sam as well. He's your man.
On Wed, Aug 26, 2015 at 5:24 AM, Eren Türkay er...@skyatlas.com wrote:
Hello operators,
I am wondering
and we generally run a much newer Horizon and Keystone than the rest of the
services. We had Horizon and Keystone on POST KILO (master after Kilo
released) while still running Juno on all other services. Worked fine.
On Wed, Aug 26, 2015 at 11:09 AM, David Medberry openst...@medberry.net
wrote:
On 26/08/15 19:11, David Medberry wrote:
and we generally run a much newer Horizon and Keystone than the rest of
the services. We had Horizon and Keystone on POST KILO (master after
Kilo released) while still running Juno on all other services. Worked fine.
Horizon used to work cross versions
Hi,
I want to restrict Avzones to particular Tenant so that users in the Tenant
can only see the particular Avzone from drop down while provisioning
instances.
Thanks
___
OpenStack-operators mailing list
OpenStack-operators@lists.openstack.org
Hello operators,
I am wondering if anyone is using different versions of Openstack in different
sites.
We have our first site which is Juno, and we are now having another site where
we are planning to deploy Kilo. Does anyone have experience with different
versions of installation? Particularly,
James,
Great stuff! Please see @PCM in-line...
On Tue, Aug 25, 2015 at 6:26 PM James Dempsey jam...@catalyst.net.nz
wrote:
Oops, sorry about the blank email. Answers/Questions in-line.
On 26/08/15 07:46, Paul Michali wrote:
Previous post only went to dev list. Ensuring both and adding a
On 26-08-2015 17:17, Jonathan Proulx wrote:
We recently upgraded from Juno to Kilo and many of our clients
(including Horizon) are still Juno with no problems.
Great news. That's our use case. We will have Juno clients and Kilo API
endpoints.
Thank you for your help.
--
Eren Türkay, System
Juno clients with Kilo endpoints are fine.
We recently upgraded from Juno to Kilo and many of our clients
(including Horizon) are still Juno with no problems.
We also had a Kilo Horizon (for testing) running against Juno
endpoints prior to the upgrade and that seemed to work as well but it
Hello,
As you know, much discussion has been around the naming and the url pathing for
the ip-usages extension. We also discussed this at the neutron mid-cycle as
well. Since we are the ones the made the extension, we use the extension to
help with scheduling in our layer 3 network design.
On 8/26/2015 9:30 AM, Eren Türkay wrote:
On 26-08-2015 17:17, Jonathan Proulx wrote:
We recently upgraded from Juno to Kilo and many of our clients
(including Horizon) are still Juno with no problems.
Great news. That's our use case. We will have Juno clients and Kilo API
endpoints.
Thank
On 26/08/15 23:43, Paul Michali wrote:
James,
Great stuff! Please see @PCM in-line...
On Tue, Aug 25, 2015 at 6:26 PM James Dempsey jam...@catalyst.net.nz
SNIP
1) Horizon compatibility
We run a newer version of horizon than we do neutron. If Horizon
version X doesn't work with
On 27 August 2015 at 06:48, raju raju.r...@gmail.com wrote:
Hi,
I want to restrict Avzones to particular Tenant so that users in the Tenant
can only see the particular Avzone from drop down while provisioning
instances.
Hi Raju,
I don't think it's possible at the moment, however there is
Yeah we run a multitude of versions at the same time. We usually run N and N-1
in the same env but have also done N-2 (eg. Havana, Icehouse and Juno)
Currently we are mainly Juno (keystone, heat, ceilometer, cinder) with a couple
of icehouse things lying around. We are in the progress of
On Thu, Aug 27, 2015 at 11:26:42 +1000, Marcus Furlong wrote:
On 27 August 2015 at 06:48, raju raju.r...@gmail.com wrote:
Hi,
I want to restrict Avzones to particular Tenant so that users in the Tenant
can only see the particular Avzone from drop down while provisioning
instances.
you
Hi,
There is only region endpoint filter currently, I did not find a way to
restrict Availability Zones visibility for tenants. I think it could be a user
story or discuss this in openstack-dev maillist:
openstack-...@lists.openstack.orgmailto:openstack-...@lists.openstack.org
region
15 matches
Mail list logo
