that's an approach
How about random instance gateway for LB ?
or
Add one more component to responsible for network-healthy?
2011/4/28 Tushar Patil
> Dear All,
>
> We (NTT PF Lab) will be discussing on how we can support HA of nova-network
> component tomorrow at 4:00 P.M.
> Actually Edward
Hello openstackers ,
This is Hugo Kuo
There's a topology as the link , in this design . HA and LB will be set in
app layer with two zones for fault tolerance . Due to there's no any idea
about nova-network host HA in my mind.
http://hugokuo-hugo.blogspot.com/2011/06/method-of-web-service-halb-in-o
Hello Diego ,
How's your new release version
Is that good to work ? I did not test it . Maybe I'll play with new release
next week.
btw , the test cloud for myself which made by Stackops is still running well
.
Just say hi and a report
Cheers
HugoKuo
2011/5/26 Diego Parrilla Santamaría
> H
Thanks Oleg ,
It's a good experience share.
Especially the live-migration and snapshot section . It's really valuable
for me.
Our approach is very similar withe mirantis. The difference is on storage
device , AMI has product our own Storage device for backup etc. What I have
to operate just set iS
1.Mysql
2.FlatDHCP
3.Manually from ubuntu PPA
1head node
1network+volume
6compute ndoes
I'm hard working on nova-network HA solution.My purpose is avoid the
interruption btween user and instance.
Current topology , instance must traffic from nova-network.
Two consideration.
1. Add one more nova-
work servers. This ensures that nova-api knows
> which nova-network instance to use to reach any particular project
> network.
> -nld
>
> On Tue, May 10, 2011 at 9:08 PM, 郭耀謙 wrote:
> > Hello , guys
> > There's a problem while separate instance's network and nova
Hello , guys
There's a problem while separate instance's network and nova-management
network.
EX.
Nova management network : 192.168.1.0/24 eth0
Instance network : 10.0.0.0/12 eth1 bridge to br100
During cloud-setup :
Instance try to retrieve metadata from 169.254.169.254.
I
I think the problem is your proxy sever
> > I use firefox to visit the URL:”
> > https://bugs.launchpad.net/nova/+bug/771489”, but it failed every
> time,just
> > like this:
> >
> > 位于 bugs.launchpad.net 的服务器响应时间过长。
> >
>
bugs.launchpad.net sever request timeout
> >
> >
> >
> >
> > * 此站点暂
郭耀謙 於 2011年5月5日下午9:15 寫道：
> I hope someone can discuss with me there're two diagrams
>
>
> http://hugokuo-hugo.blogspot.com/2011/05/thinking-about-possibility-of-these-map.html
>
> *Note* Public network==Corporate network
>
> *My purpose *
> goal1- Access in
I hope someone can discuss with me there're two diagrams
http://hugokuo-hugo.blogspot.com/2011/05/thinking-about-possibility-of-these-map.html
*Note* Public network==Corporate network
*My purpose *
goal1- Access instance from public network cloud users.
goal2- Using euca2ools to control ope
+3
2011/4/15 Chris Behrens
> +2
>
>
> On Apr 14, 2011, at 9:07 AM, Sandy Walsh
> wrote:
>
> I've been getting a lot of questions about Zones lately.
>
> How much interest is there for an informational session on Zones and, I
> guess, Distributed Scheduler and roadmap?
>
> (pending an avail
11 matches
Mail list logo
