Thanks Mark.Excellent - better to find the conflicts now than later.On a related note, we should also have media types (and supporting RFCs) for the appropriate http interactions. We did that for CDMI (http://tools.ietf.org/html/rfc6208) Makes it easy for ops and implementations ...Cheersk/
Hi!
As I stated on our Skype chat about this the other day, I think that
the default port for HTTP services should be 80, with 8080 used for
administrative endpoints. Unless there's a good reason to have a
specific port assigned to what is essentially just an HTTP service, I
don't think we should
I'd prefer to keep it convenient to develop and demo on a single
machine. I don't think there is any added inconvenience during
deployment if the ports are not the standard http ports.
On Fri, Jun 24, 2011 at 12:15 PM, Jay Pipes jaypi...@gmail.com wrote:
Hi!
As I stated on our Skype chat
This might helpful to understand the network setup.
http://blog.stackops.com/2011/06/13/understanding-stackops-openstack-nova-networking-configuration/
Thanks
On Fri, Jun 24, 2011 at 7:39 AM, tianyi wang wangc...@gmail.com wrote:
Hi All,
I have two PC with same hardware
Hi Alex,
I advise you to start with a flatdhcp configuration and change to
vlan, when everything else works. Don't forget if you like to use vlan
mode, your switch must support it, and you need to configure the vlans
on the switch.
Best Regards,
Márton Kiss
Xemeti
2011/6/24 tianyi wang
If you are considering FlatDHCP instead of VLAN, may be our distro can help
you: http://www.stackops.org
Still, you can manually change a running Stackops deployment to VLAN. It's
not a daunting task for an environment like yours.
Diego
P.D.: Sorry for this rather 'bizdev mode' announcement.
--
6 matches
Mail list logo
