On Sat, Apr 07, 2012 at 08:53:12PM -0400, Nathanael Burton wrote:
> Better yet why not add support in Glance for automatically determining
> those things (distro, versions, etc)[1]. That way you don't have to rely on
> people doing the right thing.
[Sorry I'm a little late to the party]
Just a no
On Tue, 10 Apr 2012, Justin Santa Barbara wrote:
> Signing would definitely be a great v2 feature. For v1, we just need some
> way to know that an image is provided by the cloud provider, and some idea
> of what that image "is".
>
> I believe every cloud is stuck respinning their own images, beca
Signing would definitely be a great v2 feature. For v1, we just need some
way to know that an image is provided by the cloud provider, and some idea
of what that image "is".
I believe every cloud is stuck respinning their own images, because we
haven't been able to agree a "golden image" standard
On Sat, 7 Apr 2012, Justin Santa Barbara wrote:
> Is there a (de-facto) standard for image metadata/properties? I'd like to
> be able to able to launch e.g. the Debian Squeeze image provided by the
> cloud. This is particularly important for clouds that don't allow image
> upload, but likely thi
>
>
>> Are the major and minor numbers going to be sufficient versioning
>>> information? See for example PEP 386 for more detailed version strings (
>>> http://www.python.org/dev/peps/pep-0386/).
>>>
>>
>> For a distro, I believe yes. Do you have a counter-example?
>>
>
> Not off the top of my he
On Mon, Apr 9, 2012 at 12:40 PM, Justin Santa Barbara
wrote:
> On Mon, Apr 9, 2012 at 8:18 AM, Doug Hellmann > wrote:
>
>> I'm thinking of the os prefix as standing for OpenStack, not Operating
>>> System.
>>>
>>
>> I would never have guessed that from the context. Why OpenStack instead
>> of Ope
On 04/09/2012 02:41 PM, Justin Santa Barbara wrote:
I should probably clarify my terminology a little here, as I may have
mangled it:
* I'm talking about additional/extension properties, not properties
that are well-known to Glance
* However, we agree to use a common set of properties
I should probably clarify my terminology a little here, as I may have
mangled it:
- I'm talking about additional/extension properties, not properties that
are well-known to Glance
- However, we agree to use a common set of properties to mean certain
things.
In other words, we all agre
On 04/07/2012 06:13 PM, Justin Santa Barbara wrote:
Is there a (de-facto) standard for image metadata/properties? I'd like
to be able to able to launch e.g. the Debian Squeeze image provided by
the cloud. This is particularly important for clouds that don't allow
image upload, but likely this w
On Mon, Apr 9, 2012 at 8:18 AM, Doug Hellmann
wrote:
> I'm thinking of the os prefix as standing for OpenStack, not Operating
>> System.
>>
>
> I would never have guessed that from the context. Why OpenStack instead of
> Operating System?
>
We reserve this limited region of the namespace (opensta
On Sat, Apr 7, 2012 at 6:13 PM, Justin Santa Barbara wrote:
> Is there a (de-facto) standard for image metadata/properties? I'd like to
> be able to able to launch e.g. the Debian Squeeze image provided by the
> cloud. This is particularly important for clouds that don't allow image
> upload, bu
On Apr 7, 2012 9:25 PM, "Justin Santa Barbara" wrote:
>
> Thanks Padraig & Nathanael - virt-inspector is a great source of
inspiration. Can we put the virt-inspector output into a glance property?
Would all the clouds agree to do that?
>
> I still would also like simpler metadata, as it just fee
On 04/08/2012 02:25 AM, Justin Santa Barbara wrote:
> Thanks Padraig & Nathanael - virt-inspector is a great source of inspiration.
> Can we put the virt-inspector output into a glance property? Would all the
> clouds agree to do that?
>
> I still would also like simpler metadata, as it just f
Thanks Padraig & Nathanael - virt-inspector is a great source of
inspiration. Can we put the virt-inspector output into a glance property?
Would all the clouds agree to do that?
I still would also like simpler metadata, as it just feels like too much
information and work required for what is a c
Looks like Pádraig and I were thinking alike.
On Apr 7, 2012 8:49 PM, "Pádraig Brady" wrote:
> On 04/07/2012 11:13 PM, Justin Santa Barbara wrote:
> > Is there a (de-facto) standard for image metadata/properties? I'd like
> to be able to able to launch e.g. the Debian Squeeze image provided by t
Better yet why not add support in Glance for automatically determining
those things (distro, versions, etc)[1]. That way you don't have to rely on
people doing the right thing.
Nate
References:
[1] -
http://libguestfs.org/virt-inspector.1.html#getting_inspection_data_from_the_libguestfs_api
On A
On 04/07/2012 11:13 PM, Justin Santa Barbara wrote:
> Is there a (de-facto) standard for image metadata/properties? I'd like to be
> able to able to launch e.g. the Debian Squeeze image provided by the cloud.
> This is particularly important for clouds that don't allow image upload, but
> like
I'm talking here about publicly accessible attributes of images, that the
image owner would set, so that API callers could select the right image
with which to launch their instances.
e.g. I'm trying to launch a Zookeeper cluster made up of 5 instances on 5
different clouds; how can I figure out w
Is there a (de-facto) standard for image metadata/properties? I'd like to
be able to able to launch e.g. the Debian Squeeze image provided by the
cloud. This is particularly important for clouds that don't allow image
upload, but likely this will remain useful because different clouds will
have d
19 matches
Mail list logo
