Hi,
On 05/12/2012 03:11 AM, Thomas de Looff wrote:
Hi,
On 12 May 2012, at 2:20 AM, Chiradeep Vittal wrote:
On 5/11/12 9:21 AM, "Salvatore Orlando"
wrote:
Hi,
IPv6 would be a dramatic improvement for Cloudstack networking,
I totally agree on that
+1
and I would like to spend some d
I'd like to be a part of the mailing list on this account, rather than my
work account.
Thanks,
Hello,
I’m running into more and more instances where it’s required to directly
interact with the Cloudstack database, and I find myself having to reverse
engineer it. So, the question is, does an up to date data dictionary exists
for the Cloudstack database?
Thanks,
Charles Russell
Senior
+1
Kind Regards
Giles
D: 020 3603 0541 | M: 07961112055
-Original Message-
From: Charles Russell [mailto:charles.russ...@kisinc.net]
Sent: 14 May 2012 17:43
To: cloudstack-dev@incubator.apache.org
Subject: Data Dictionary
Hello,
I’m running into more and more instances where it’s requ
Though I think directly access database is not a good idea, the database schema
is at setup/db/create-schema.sql in source
> -Original Message-
> From: Charles Russell [mailto:charles.russ...@kisinc.net]
> Sent: Monday, May 14, 2012 9:43 AM
> To: cloudstack-dev@incubator.apache.org
> Subj
I have had to revert to manipulating things in the database on more than one
occasion, but only on test and POC systems, you should not go near it on a live
system
-Original Message-
From: Frank Zhang [mailto:frank.zh...@citrix.com]
Sent: 14 May 2012 18:58
To: cloudstack-dev@incubator.ap
Well the times I've had to revert to manual editing of SQL I've subsequently
posted a bug as I find them.
I had to follow the SQL constraints and delete this zone because of this
error.I successfully reversed it but it wasn't a walk in the park. And as
with everyone else.. It's not recom
Yes please, keep filing the bugs! A lot of work went into 3.0.x to fix the
most common cases of "X does not work so I need to go edit the db". We have to
keep rooting out these problems.
-kevin
> -Original Message-
> From: Charles Russell [mailto:charles.russ...@kisinc.net]
> Sent: M
First of all, it is not very clear whether or not this patch is required
for XenServer with regard to the Cloud Supplemental Pack:
http://bugs.cloudstack.org/browse/CS-14655
Could someone shed some light on this?
Secondly, I'm having an issue with CloudStack trying to use my
"cloud-private" n
I forgot to include the following information that I found in the
database after the host was added:
mysql> select * from host where id=22 \G;
[...]
private_ip_address: 10.0.0.16
private_netmask: 255.255.254.0
private_mac_address: e8:9a:8f:22:9b:c4
storage_ip_address: 10.0.0.16
storage_netmask
Hi Mohammad, Does it mean my ICLA has been filed?
-Original Message-
From: Craig Russell [mailto:papa...@gmail.com] On Behalf Of Craig L Russell
Sent: Wednesday, May 02, 2012 6:36 AM
To: Edison Su
Cc: secret...@apache.org; Frangillen Romero; priv...@incubator.apache.org
Subject: Re: Apache
Hi folks,
We had some chatter on private@ list regarding the approrpiateness of
announcing the 3.0.2 release on the ASF-hosted lists - and that turned
into a discussion of where we go from here with regards to releases
with a few opinions circling on whether we should assume that it's the
last rel
Yes :), congrats, I will work on sending the request for your account
creation.
On Mon, May 14, 2012 at 8:50 PM, Edison Su wrote:
> Hi Mohammad, Does it mean my ICLA has been filed?
>
> -Original Message-
> From: Craig Russell [mailto:papa...@gmail.com] On Behalf Of Craig L
> Russell
> S
My concern here is that the roadmap has lots of new features, and we do not
want to be waiting 6 months for the next release which was due out in May
Geoff
-Original Message-
From: David Nalley [mailto:da...@gnsa.us]
Sent: 14 May 2012 20:07
To: cloudstack-dev@incubator.apache.org
Subject
Matthew,
It looks like you have forgot to label your physical networks and map them
within the Zone Setup process, this is vital if you want to use dedicated NICs
for any of the four network types, ie Management, Guest, Public or Storage.
Re the Cloud Supplemental Pack, this is only required if
On Mon, May 14, 2012 at 3:13 PM, Geoff Higginbottom
wrote:
> My concern here is that the roadmap has lots of new features, and we do not
> want to be waiting 6 months for the next release which was due out in May
>
> Geoff
>
A valid point - though it's worth pointing out that the roadmap you
ar
Please see my responses inline, below:
On 5/14/2012 3:18 PM, Geoff Higginbottom wrote:
Matthew,
It looks like you have forgot to label your physical networks and map them
within the Zone Setup process, this is vital if you want to use dedicated NICs
for any of the four network types, ie Manag
Matthew,
If I understand correctly, your storage is on a different IP Range to your
Management Server and Hosts etc, if this is the case you need a Storage
Network, which also needs to be accessible from the Management Server. If no
Storage Network is configured, CloudStack will use the Manage
Thanks for the response. So then my next question is how would this be
achieved? I can see creating a network for the db servers and set all db
instances to use it as their default network, and attach the app servers _to_
the db network but then there would be no filtering occurring. The app
On 5/14/12 11:09 AM, "Charles Russell" wrote:
>Well the times I've had to revert to manual editing of SQL I've
>subsequently posted a bug as I find them.
>
>I had to follow the SQL constraints and delete this zone because of this
>error.I successfully reversed it but it wasn't a walk in the
Noted,
However, I didn't delete but rather marked with a now() for the removed field.
Charles Russell
Senior Consulting Engineer
Knowledge Information Solutions, Inc.
Phone: (757) 275-7523
Cell: (757) 647-6236
Fax: (757) 486-2318
-Original Message-
From: Alena Prokharchyk [mailto:ale
On 5/14/2012 3:35 PM, Geoff Higginbottom wrote:
Matthew,
If I understand correctly, your storage is on a different IP Range to your
Management Server and Hosts etc, if this is the case you need a Storage
Network, which also needs to be accessible from the Management Server. If no
Storage Ne
David,
My 2 cents (and possibly drawing flames myself):
During the transition period (and beyond), Citrix is going to do what it
needs to do as a commercial entity. While this list is intended to focus
on the ASF project itself, it's going to take time for an official Apache
release to be approv
On 5/14/12 1:11 PM, "Charles Russell" wrote:
>Noted,
>
>However, I didn't delete but rather marked with a now() for the removed
>field.
It can lead to NPEs on all API calls returning the objects having
references to the zone object, as by default we make an object search with
"don't include rem
On Mon, May 14, 2012 at 3:26 AM, Wido den Hollander wrote:
>
> On 05/12/2012 03:11 AM, Thomas de Looff wrote:
>>
>> I don't think this is a good idea. I think we have to make step one and two
>> at the same time.
>> Or maybe start with step two, so you can assign public ip's to your VM when
>> y
I had assumed you had Primary and Secondary storage on different IP ranges to
your Management Server which does need to be able to access Secondary Storage
but not Primary Storage.
I now note your Primary Storage is iSCSI, and that you had a failure of all
Hosts.
When adding Storage and Hosts,
Forgot to add, re the patch http://bugs.cloudstack.org/browse/CS-14655. I was
doing a big POC build with some of the Citrix engineers last week and they
highlighted that this patch should be applied for XenServer 6.x and we were not
using Security Groups so had not installed the CSP Package.
Ki
On 5/14/2012 4:48 PM, Geoff Higginbottom wrote:
I had assumed you had Primary and Secondary storage on different IP ranges to
your Management Server which does need to be able to access Secondary Storage
but not Primary Storage.
That assumption is correct, Primary Storage is on a different su
David,
I'm not sure how this fits with the Apache model, but as a user of
CloudStack, I would prefer that Citrix continue to release updates to
3.0.x until an Apache release is ready.
Keeping momentum going with releases is important, especially when there
are a few user affecting bugs (e.g. VNC,
Matthew,
Removing and then re-adding Pri Storage will not wipe the LUNs and the existing
VHD files which are there, assuming the associated Guest Instances are still in
the database should also remap.
How to avoid this in the future? It's pretty rare for a XenServer cluster to
bomb out in this
It is fair for David to remind us that a big part of that the
transition is the role of the community in what's being released.
With best will in the world, I suspect that's gonna take some time, so...
+1 to the sentiment for frequent releases, even if by Citrix (and +1
to us monitoring/paying at
+1 for James proposal: CloudStack has a strong momentum right now but the cloud
space is evolving very fast and loosing momentum could mean a strong reversal
of adoption.
If moving to ASF is to delay CloudStack development cycle, then there is a big
problem. Schedule must be more aggressive, not
Agreed with this..
I think that people are using cloudstack as the compute stack right now
because its more advanced than the other ones on the market.
The other big open source project has momentum so I think it really
important that the schedule for releases stays on the aggressive side!
my 2 c
One way to do is to have iptables do filtering on db-servers, but the easiest
is ...
Have a advance zone, create two accounts, put db VMs in one account (guest
network) and webserver VM in another. Now in general you have several options
to control the traffic to these accounts via the VR.
For e
On Mon, May 14, 2012 at 4:15 PM, Chip Childers
wrote:
> David,
>
> My 2 cents (and possibly drawing flames myself):
>
> During the transition period (and beyond), Citrix is going to do what it
> needs to do as a commercial entity. While this list is intended to focus
> on the ASF project itself,
David,
I think some lag between the last Citrix release and the first Apache
release is unavoidable.
I think it's in CloudStack's best interest if the lag is as short as
possible, rather than holding out for the next release to definitely be
Apache for ideological reasons.
Cheers,
JK.
-Or
36 matches
Mail list logo
