On Sat, Apr 1, 2017 at 5:21 PM, Matt Riedemann wrote:
> On 4/1/2017 8:36 AM, Blair Bethwaite wrote:
>
>> Hi all,
>>
>> The below was suggested for a Forum session but we don't yet have a
>> submission or name to chair/moderate. I, for one, would certainly be
>> interested in providing input. Do w
On 4/1/2017 8:36 AM, Blair Bethwaite wrote:
Hi all,
The below was suggested for a Forum session but we don't yet have a
submission or name to chair/moderate. I, for one, would certainly be
interested in providing input. Do we have any owners out there?
Resource reservation requirements:
==
The
I agree with Mr. Pipes. I’ve not used that API ever and I’ve no recollection of
anyone asking about it nor am I aware of anyone who actually uses it. I vote to
deprecate.
-Original Message-
From: Jay Pipes
Date: Saturday, April 1, 2017 at 10:02 AM
To: "openstack-operators@lists.openstac
On 4/1/17 2:16 PM, Ignazio Cassano wrote:
> Tested configuration in the cluster. Heat now works as expexted.
> Registry_host address must be the host address not the cluster vip.
> Regards
> Ignazio
Glad you got it working!
cheers,
brian
___
OpenStack
Tested configuration in the cluster. Heat now works as expexted.
Registry_host address must be the host address not the cluster vip.
Regards
Ignazio
Il 01/Apr/2017 16:40, "Ignazio Cassano" ha
scritto:
> Hi again, I hope the configuration in previous message will work when I
> 'll enable the cl
I know we've talked about this over and over and another bug [1]
reminded me of it. We have long talked about removing the ability to
specify a block device name when creating a server or attaching a volume
because we can't honor the requested device name anyway and trying to do
so just causes
My vote is to deprecate it.
On 03/22/2017 11:16 AM, Matt Riedemann wrote:
This is mostly directed at operators but I'm cross-posting to the ops
and dev lists.
First, does anyone use the os-hosts API and if so, for what use cases?
The os-hosts and os-services APIs are very similar, and they wor
Hi again, I hope the configuration in previous message will work when I 'll
enable the cluster.
I am going to test it.
Many thanks for your help.
Ignazio
Il 01/Apr/2017 15:22, "Ignazio Cassano" ha
scritto:
> Hi Brian,
> I found where is the problem
> In glance-api.conf I must setup the registry_
Hi all,
The below was suggested for a Forum session but we don't yet have a
submission or name to chair/moderate. I, for one, would certainly be
interested in providing input. Do we have any owners out there?
Resource reservation requirements:
==
The Blazar project [https://wiki.openstack.org/wik
Hi Brian, when I enable v1 and v2 api in glance-api.conf , using the same
heat template I got http 500.
Now in my glance-api.conf I have the same configuration used on ubuntu 16
(whete heat works fine):
#enable_v1_api = false
#enable_v1_registry = true
#enable_v2_api = true
#enable_v2_registry = tr
Hi Brian,
I found where is the problem
In glance-api.conf I must setup the registry_host entry and it must be
equal to the bind_host entry in the file glance-registry.conf.
So, enable v1 api and the abive parameters, heat works.
My problem is that I am using 3 controllers and the bind_host in the
Hello Ignazio. A few things:
(1) You can run both glance v1 and v2 simultaneously. They share the
same database and storage backend. The difference is that you, as a
client, interact with the APIs in different ways (v1 does a lot of
info-passing in http headers, v2 does everything in JSON; v2 h
Hi, thanks for your answer.
Heat newton on ubuntu 16.04 works fine even if images are under /v2.
On centos 7, same configuration, but it does not work
2017-03-31 20:42 GMT+02:00 Basil Baby :
> Default seems to v1
> https://github.com/openstack/heat/blob/stable/newton/heat/
> engine/clients/os/gla
On Tue, Mar 28, 2017, at 05:14 PM, Jeremy Stanley wrote:
> The Mailman listserv on lists.openstack.org will be offline for an
> upgrade-related maintenance for up to 3 hours (but hopefully much
> less) starting at 20:00 UTC March 31, this coming Friday. This
> activity is scheduled for a relatively
14 matches
Mail list logo