I confirmed that my VLAN B can reach VLAN C, and VLAN C also can reach VLAN B
.But the problem is that there is no gateway be set for VLAN B in vRouter,
there is only a default gateway for VLAN A, So the VLAN B ip address can't be
reached from VLAN C and any other VLANs.
You know if the mana
Found the solution; tags on the service offering correspond to the tags
for the ROOT disk. In case anyone else has this question. :)
On 9/13/13 4:40 PM, David Matteson wrote:
Hey everybody,
When deploying a new VM, the API call does not seem to support
specifying any tags or diskofferingid fo
Hello,
I know as of Cloudstack 4.0.1 it was not possible to set up multiple local
storage volumes on a cloudstack host. Is this still the case? I am looking to
provide multiple drives as separate volumes to simulate the kind of disk
passthrough features that are supported by VMWare.
Thank
> -Original Message-
> From: David Ortiz [mailto:dpor...@outlook.com]
> Sent: Friday, September 13, 2013 1:33 PM
> To: users@cloudstack.apache.org
> Subject: RE: Support for multiple Local Storage volumes
>
> That's actually how I have my primary storage setup using a gfs2 cluster. In
>
Hey everybody,
When deploying a new VM, the API call does not seem to support
specifying any tags or diskofferingid for the ROOT volume. Does anybody
know of a way around this?
The problem is; we have a regular HDD storage pool and an SSD storage
pool. We want some VMs (who have chosen the o
On Tue, Jun 4, 2013 at 10:18 PM, Joe Brockmeier wrote:
> ## New Features
>
> Some of the notable new features in Apache CloudStack 4.1.0 include:
>
> * Resizing root and data volumes.
I decided to play with the resize feature and found this to be not as
advertised. :) Did this turn into only resiz
Hello Dave,
I don't have a local.storage.path variable in my agent.properties file, instead
I have local.storage.uuid which is set to the uuid in the storage_pool table.
The path in the table is set to /var/lib/libvirt/images/ and as I mentioned
earlier, I tried to change it in the db with no l
Fair enough. I am running 4.0.1, so it must have been removed then. I would
restart the agent though to be safe. Might be worth asking on the dev list as
well since I would imagine someone there knows what the agent does to get its
local storage path. Let me know if you find out what the new
That's actually how I have my primary storage setup using a gfs2 cluster. In
this case I want the storage to only be local to that host though. I have some
VMs running that will work better if they have exclusive access to a spindle.
Just wanted to make sure this feature isn't already there b
Just to check, does your cluster have access to the internet? That created
some issues for us when we tried to run our cluster disconnected without adding
realhostip.com to our local dns.
> Date: Fri, 6 Sep 2013 02:41:07 -0700
> From: dj_dark_jungl...@yahoo.com
> Subject: Re: Console stopped wo
RN is not ready yet. Radhika has sent mail earlier asking for volunteers in
dev mailing list.
You should be able to pick up this commit from 4.2 branch and do upgrade like
you have done it first time, right??
https://issues.apache.org/jira/browse/CLOUDSTACK-4245
-Original Message-
F
You can always use "SharedMount" in KVM:
KVM supports "Shared Mountpoint" storage. A shared mountpoint is a file system
path local to each server in a given cluster. The path must be the same across
all Hosts in the cluster, for example /mnt/primary1. This shared mountpoint is
assumed to be a c
Travis,
Change the property local.storage.path in
/etc/cloud/agent/agent.properties.
Thanks, Dave
> Date: Thu, 29 Aug 2013 21:03:51 +0530
> Subject: Re: Change default libvirt storage pool location on KVM
> From: rajuj...@gmail.com
> To: users@cloudstack.apache.org
>
> Hello Travis,
>
Stephen,
I have NFS based SS running on a flat network alongside my guests with
basic networking with 4.0.1. I would expect that to still be viable in 4.0.2.
Thanks, Dave
> Date: Wed, 21 Aug 2013 10:17:15 +0100
> Subject: Basic Networking - 4.0.2 - Same CIDR for all networks (vmware)
>
Had a successful 4.0.1 implementation.
However, since upgrade to 4.1
Guest system, on VLAN isolated advanced network, has a public IP...
Have set egress on the network to let everything out.
Forwarding SSH, WWW, HTTPS to guest, this works just fine.
Guest is able to resolve DNS ... masq on the VR a
That's the insight I needed, and indeed, you are correct. Appreciate the very
quick response from you fellows.
Noel
> From: jayapalreddy.ur...@citrix.com
> To: users@cloudstack.apache.org
> Subject: Re: V4.1 Advanced Network, VR reboot, NAT rules gone
> Date: Fri, 13 Sep 2013 06:02:55 +
>
>
I think we can move forward as long as the installation won't be blocked by
documentation; since the documentation can be refined all the time. We can
still find tiny bugs relate to doc in 4.1 or even 4.0.
On Thu, Sep 12, 2013 at 8:44 PM, Ron Wheeler wrote:
> It is not really off topic since
Sure I could look at writing up a howto for gluster. It is pretty straight
forward.
As for the other questions; yes I am using XFS as the underlying filesystem for
gluster. For KVM, I love it. I haven't really noticed any significant issues,
what are these issues regarding HA and snapshotting?
Hi Sudha and all,
Good day to you, and thank you for your e-mail.
(1) How to get the 4.2-forward branch? I can't find any documentation on
where I can download different version and branch of CloudStack 4.2. Need
to use git to pull them from somewhere?
(2) Is there any documentation for the 4.2
On Fri, Sep 13, 2013 at 1:52 AM, alex wrote:
> Hi,
>
> I would like to setup a machine which can reach all tenant VMs in my
> advanced zone. The use case is a centralized monitoring service of tenant
> VMs.
>
> So I was thinking to create a VM on a shared network under ROOT and add new
> NICs on t
Dear Sudha and all,
In addition to my email below, I also noted that the status of the below
bug:
https://issues.apache.org/jira/browse/CLOUDSTACK-4645
has been resolved by this committed fix:
===
Commit 10486ea4dddbfe41bfc200094dd2ee5e833ed7c5 in branch refs/heads/4.2
from Venkata Siva Vijayen
Are you rebooting the VM with the "reboot" command in the VM? If so,
try the rebootRouter API or the UI instead. There's no agent in the
virtual router so CloudStack may not be aware of a reboot performed
outside of CloudStack. This is even the case for a reboot of a virtual
router by vSphere na
How are you rebooting the VR? Through CloudStack or outside?
On 13/09/13 5:10 AM, "Noel Kendall" wrote:
>FW rules are not persistent in VR? I am trying to figure out why a V4.1
>VR does not properly NAT, and of course,reboot several times to reset
>state. I see that after each reboot, the NAT r
Who is volunteering to provide the list of Fixed issues for the RN?
-Original Message-
From: Animesh Chaturvedi [mailto:animesh.chaturv...@citrix.com]
Sent: Wednesday, August 28, 2013 4:40 AM
To: d...@cloudstack.apache.org; users@cloudstack.apache.org
Subject: RE: Volunteers to Complete t
Fix has been posted already on 4.2 forward and 4.2 branches by Vijay.
-Original Message-
From: Milamber [mailto:milambersp...@gmail.com]
Sent: Thursday, September 12, 2013 12:40 PM
To: users@cloudstack.apache.org
Subject: Re: URGENT: Unable to upgrade from 4.1.1 to 4.2.0
Le 12/09/2013
Hi,
Rebooting the VR outside the cloudstack, will not program the NAT/firewall
rules.
If you reboot the VR from the cloudstack then rules get programmed.
Thanks,
Jayapal
On 13-Sep-2013, at 5:10 AM, Noel Kendall
wrote:
> FW rules are not persistent in VR? I am trying to figure out why a V4.1
Hi,
In shared network VR does not act as a gateway for any of the network. So your
network infrastructure has to take care of the reachability from one vlan to
another vlan. i.e. on your gateway make sure that you have a route to reach
from Vlan B to Vlan C
Thanks,
Sanjeev
-Original Messa
Hi,
To revert back, please see my comments inline.
Thanks,
Jayapal
On 13-Sep-2013, at 12:05 AM, Indra Pramana wrote:
> Dear all,
>
> I proceed to upgrade my CloudStack 4.1.1 to 4.2.0 by compiling it from
> source. However, after upgrading the management servers and all the KVM
> hosts, I am no
wow, that would suck real bad! hope this get fixed soon with proper QA.
On Thu, Sep 12, 2013 at 4:33 PM, Arnaud Gaillard <
arnaud.gaill...@xtendsys.net> wrote:
> This is a known issue
>
>
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201309.mbox/%3C52307BF2.203%40apache.org%3E
>
Hi,
I would like to setup a machine which can reach all tenant VMs in my
advanced zone. The use case is a centralized monitoring service of tenant VMs.
So I was thinking to create a VM on a shared network under ROOT and add new
NICs on the same network to the machines of the 3 tenants in order to
Just wanted to say thank you to everyone over the past couple weeks for
answering all of the questions I have had. I am a cloudstack convert from
vmware, so it has taken me a bit of time getting used to everything in
cloudstack.
31 matches
Mail list logo
