openstack team mailing list archive

[Rick Harris <rick.harris@xxxxxxxxxxxxx>]

> streaming should be done inside nova-compute, rather than in a xapi plugin...
do you _need_ the code inside a plugin for xs-snapshots, or will it be OK if we move it?

If we moved the code into nova-compute, wouldn't that mean we're directing
all image-download/image-snapshot traffic through the compute node?

Swift -> Glance -> Compute -> XS-Host

Since we're going to have far fewer compute nodes than XS-Hosts, wouldn't it
be better to bypass compute-node entirely?

Swift -> Glance -> XS-Host

>From a maintenance/deployment/code-reuse perspective, I agree a plugin is less-than-ideal, but I think, considering the tradeoffs, it solves the problem quite nicely.

> Assuming that that’s OK, where should this code go?

The ImageService is probably not the right place for it since, as I understand
it, it's an API-level abstraction for image discovery and description.

We probably need a similar abstraction at the Compute-level which abstracts
image uploading and fetching.

However, this may be moot at some point, as the API and Compute-level could
eventually delgate both responsibilities to Glance.

> I was also expecting Sateesh to implement the Glance authentication, once Jay
is finished with middleware-authentication.  Was anyone else expecting to do
this?

We've been punting on auth for the moment. If you guys have a good idea of
where to go with it, please do!

> What is the intended semantics of the Glance x-image-meta-type header values “raw” vs “machine”?

If I'm remembering correctly, we lifted that from the Image model that was
orginally defined-but-commented-out in Nova.  It's not being used yet, but the
idea would be that values would include ("raw", "machine", "kernel",
"ramdisk").

> IANA Ports

Agreed, 80/443 make sense.
________________________________________
From: openstack-bounces+rick.harris=rackspace.com@xxxxxxxxxxxxxxxxxxx [openstack-bounces+rick.harris=rackspace.com@xxxxxxxxxxxxxxxxxxx] on behalf of Jay Pipes [jaypipes@xxxxxxxxx]
Sent: Monday, January 03, 2011 9:20 AM
To: Ewan Mellor
Cc: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] Use of IANA-registered ports

On Sun, Jan 2, 2011 at 8:57 PM, Ewan Mellor <Ewan.Mellor@xxxxxxxxxxxxx> wrote:
> For Nova, I think we're OK with the HTTP ports, because most of the components are using rabbitmq for communication.  For Glance, I'm not sure.

Good discussion on the port assignments, and after further thought,
what Eric said about using 80/443 for HTTP-based API servers is the
correct default.

As for Glance, there are two services, both HTTP REST-based services,
one for the registry node and one for the API node.  Of course, both
can be run on the same physical machine. I don't see any reason not to
stick with 80/443 for the both the API and registry servers and
configuring an alternate port for the registry server when it is being
run on the same physical machine.

-jay

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp


Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is prohibited.
If you receive this transmission in error, please notify us immediately by e-mail
at abuse@xxxxxxxxxxxxx, and delete the original message.
Your cooperation is appreciated.