We have 29 physical hosts connected to a management server in our staging
environment running CS 4.0.1. When we restart the management console the
hosts all go into a disconnected -> connecting -> disconnected state over
and over, sometimes for hours. Can anyone tell me how CS checks to see if a
ho
I will +1 this. I spoke with Cisco a few weeks ago and they certainly see
VXLANS as being the future for cloud infrastructures. In addition to Linux
support we should look at the Cisco 1000v and open vSwitch support a well.
Cisco said they already have VMWare support today on the 1000v with KVM
When I become reliable I am certainly willing to learn how to do it.
Justin
Sent from my iPhone
On May 2, 2013, at 5:50 AM, Rohit Yadav wrote:
>
>
> On Thu, May 2, 2013 at 4:30 AM, Justin Grudzien wrote:
>> It is currently in master but I will see if I can get Rohit, who I
arcus Sorensen wrote:
> The wiki was the one that had the 'display' parameter shown. I'm assuming
> the display parameter is only in master then?
>
>
> On Wed, May 1, 2013 at 2:56 PM, Justin Grudzien wrote:
>
>> Which documentation are you referring
Which documentation are you referring to? I updated cloudmonkey to add the
set display and I updated the wiki to include the changes. I also noticed
the async issue but haven't gotten around to fixing it yet.
On Wed, May 1, 2013 at 8:47 AM, Marcus Sorensen wrote:
> I noticed that the documentat
> unless you want to invest in a Netscaler for these services).
>
> Not sure that VXLAN will solve your problems since that has scaling
> problems as well. On vSphere an NX1000v DVS can only handle about 64
> hypervisors IIRC.
>
>
>
> On 4/9/13 5:39 AM, "Justin G
using a basic zone?
> With security groups you can have *lots* (thousands of) with very small L2
> networks.
>
> On 4/8/13 10:28 PM, "Justin Grudzien" wrote:
>
>> My team has been working for three weeks with CloudStack architecture
>> design and we are stru
My team has been working for three weeks with CloudStack architecture design
and we are struggling to put together a network architecture that we feel will
scale. From everything I can tell, CloudStack requires a a very large layer 2
network when using shared guest networks. We are looking to de
cessary comments, if we want them we should put them on each
> method
>
> Signed-off-by: Rohit Yadav
>
> commit 9fbae8579923ad7f2823c084e6112b406714652b
> Author: Rohit Yadav
> Date: Fri Apr 5 22:56:07 2013 +0530
>
> cli: Make cloudmonkey.py pep8 compli
wrote:
> On Mon, Apr 1, 2013 at 4:26 PM, Justin Grudzien wrote:
>
>> Thanks for the information. If you haven't already put the patch for review
>> I would like to do so and follow the directions so I can get used to the
>> process. Let me know. Also, I saw the lambda func
uot;name": "DefaultIsolatedNetworkOfferingWithSourceNatService"
},
{
"name": "DefaultIsolatedNetworkOffering"
},
{
"name": "DefaultSharedNetscalerEIPandELBNetworkOffering"
},
{
"name": "DefaultIsolatedNetworkOfferingForVpcNetworks"
},
{
"name": "DefaultIsolatedNetworkOfferingForVpcNetworksNoLB"
},
{
"name": "Test Network Offering"
}
]
}
Thanks,
Justin Grudzien
for all the help so far.
Justin
On Mon, Apr 1, 2013 at 8:52 AM, Chip Childers wrote:
> On Mon, Apr 01, 2013 at 05:56:11AM -0500, Justin Grudzien wrote:
> > Thanks for the information. If you haven't already put the patch for
> review
> > I would like to do so and follow
for future please use review board or share git formatted patch
> which would apply cleanly on master.
>
> Regards.
>
> On Mon, Apr 1, 2013 at 10:42 AM, Justin Grudzien
> wrote:
>
> > Greetings,
> >
> > I am posting my first patch. I am not sure exactly how t
efault
+elif( key == "display" ): # this key is deprecated
+config = write_config(get_attr, config_file, True)
+set_attr( key, "default" ) # set default
+else:
+missing_keys.append(key)
if
My company is building a private cloud and we are moving to cloudstack. As
we begun investigating the cloudmonkey CLI we found that the output was
slightly hard to read. I have begun working on some optimizations that I
think will benefit the community and I reached out to Rohit, who
recommended th
SHA256 passwords, then maybe you should use SHA512
> passwords in ACS. ;)
>
> John
> http://www.insidepro.com/eng/egb.shtml
>
> On Mar 29, 2013, at 4:36 PM, Justin Grudzien
> mailto:grudz...@gmail.com>>
> wrote:
>
> I apologize for jumping into this conversa
I apologize for jumping into this conversation late, but I am new to the
developer mailing list. Why would we choose SHA256+salt over SHA512+salt?
SHA512+salt's storage is insignificant when compared to SHA256 and the chances
of a birthday attack are significantly reduced. As a security professi
17 matches
Mail list logo
