Hi All,
I've created a CloudStack 4.3.2 release, with the following artifacts up
for a vote:
Git Branch and Commit SHA:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.3
Commit: a15acb8e74d52bdd973f613c19dc3afd42771be4
List of changes:
https://git-wip-us.apache
Dear all,
We are using CloudStack 4.2.0 with KVM hypervisors.
Is there a way to prevent our virtual routers (VRs) to be targeted by DNS
amplification attack? It seems that the DNS services on dnsmasq running on
the VRs are by default recursive, causing it to easily be targeted for DNS
amplificati
Indra, did you observe this on Shared Network - I had same issue with
Shared Network (public IPs) in Advanced Zone.
I think VR for VPC is NOT a problem...
On 15 December 2014 at 13:13, Indra Pramana wrote:
>
> Dear all,
>
> We are using CloudStack 4.2.0 with KVM hypervisors.
>
> Is there a way t
Please refer the following ticket, It will help
https://issues.apache.org/jira/browse/CLOUDSTACK-5494
Thanks,
jayapal
On 15-Dec-2014, at 5:52 PM, Andrija Panic wrote:
> Indra, did you observe this on Shared Network - I had same issue with
> Shared Network (public IPs) in Advanced Zone.
>
> I
Hi Andrija,
Yes, it's on a shared network with public IP in advanced zone. So far I
don't see similar issues on my VPC's VRs, but it could be because the IP is
not known, unlike the VR on a shared network which will automatically use
the second IP on the subnet after the gateway (e.g. x.x.x.2).
I
you got response with BUGs on jira and temp fix is there...
so, yes
On 15 December 2014 at 13:49, Indra Pramana wrote:
>
> Hi Andrija,
>
> Yes, it's on a shared network with public IP in advanced zone. So far I
> don't see similar issues on my VPC's VRs, but it could be because the IP is
> not kn
ACS 4.4.2 and Xenserver 6.2
When I try to deploy a template that is using cloud-ini and the VR is on the
other the VM can't connect to the meta data. When the VR and VM is on the
same host it works with no issue and now that I have migrated the VR back a
forth a few times it not an issue until
Ok, I will test that out and see how it goes. Thanks to both of you!
- Billy
-Original Message-
From: benoit lair [mailto:[email protected]]
Sent: Friday, December 12, 2014 4:18 AM
To: [email protected]
Subject: Re: Export VMs
In practice, it works.
I had to do this in
I have an issue where I can create Virtual Machines of Medium or smaller
CPU, and < 100G disk space, but anything larger throws an
InsufficientServerCapacityException. (I have 36 CPU cores, 256G RAM and
>10TB of storage available).
Where are these limits stored? After the instance is created, I
From the logs it appears that your hosts (6,1,3) are in disconnected state.
Not sure how many hosts you have in total.
Look at that part of the logs where the planners are looking for available
capacities for this VM, that will give you more insight into what is happening.
-abhi
> On 15-Dec-20
That is all three xenserver hosts that I have. It's strange -- I'm getting
those "disconnected" messages in the logs, but immediately after I get the
"state is determined to be Up". I see all three in the UI and they appear
to be healthy. I can create new Virtual Machines (of a sufficiently smal
Hi,
we're currently running a test-installallation of ACS 4.4.1 w/ XenServer
6.2. The Zone is setup as "Advanced Zone" with VLAN as isolation method.
Configured are "Shared IP"-networks as well as isolated ones.
Sometimes, if a new VM is deployed with an additional, new isolated
network, the corre
Just an FYI that I'll have to abstain from voting on this one as I'm still
in the process of testing the current 4.5.0 RC.
On Mon, Dec 15, 2014 at 2:26 AM, Rohit Yadav wrote:
>
> Hi All,
>
> I've created a CloudStack 4.3.2 release, with the following artifacts up
> for a vote:
>
> Git Branch and
If you can make bigger chunk of management server logs (via dropbox etc) then
someone may be able to provide more insight.
I am not sure if patching can cause any issues. The min requirement is that all
the Xens in the cluster should be at the same patch level.
But yes you need to take care of th
I have advanced shared networking with a public address being assigned to
each VM. The VR doesn't show having a public IP this way but the guest IP is
a public one. Should I change the Vlans and trunks to having a private
address and let the VR setup the default networking with a private range and
Hi Matthew,
To my understanding your guest Nic in XenServer and CS should remain untagged
while the associated VLAN ports in your Switch should be tagged.
Cheers,
Paul
> On 15 Dec 2014, at 16:44, Matthew Midgett
> wrote:
>
> I have advanced shared networking with a public address being assi
Correct that is the way that I have it setup. CS creates a tagged network as
shown in this example
http://mirror.charlottecolo.com/cloudstack/xennetwork.jpg
All the VM's can ping its gateway on the router. All the VM can ping any
public address. The VM's can only ping the VM's on their hypervisor
Have you checked to ensure the entire VLAN Guest traffic ranges e.g. 500 - 550
specified in CS are subsequently tagged?
> On 15 Dec 2014, at 18:52, Matthew Midgett
> wrote:
>
> Correct that is the way that I have it setup. CS creates a tagged network as
> shown in this example
> http://mirr
I just created the following Network service
Description SharedRoutedNetwork
State Enabled
Guest Type Shared
label.persistentNo
Egress Default Policy Allow
AvailabilityOptional
Created by system No
Specify VLANYes
Specify IP ranges Yes
Conserve mode Yes
N
On Mon, Dec 15, 2014 at 9:17 PM, Matthew Midgett <
[email protected]> wrote:
>
> I just created the following Network service
>
> Description SharedRoutedNetwork
> State Enabled
> Guest Type Shared
> label.persistentNo
> Egress Default Policy Allow
> Availab
It should be just the plan without assigning any ip
> On 15 Dec 2014, at 21:17, Matthew Midgett
> wrote:
>
> I just created the following Network service
>
> Description SharedRoutedNetwork
> State Enabled
> Guest TypeShared
> label.persistent No
> Egress Default Policy Allow
> Avai
I want the virtual router to do this so the customer can control the rules
themselves inside of CloudStack. My router has to be configured by me.
-Original Message-
From: Erik Weber [mailto:[email protected]]
Sent: Monday, December 15, 2014 3:25 PM
To: [email protected]
Subje
I should make the GW 10.0.1.1 and set the range from .1 to .254 so when the
VR spawns it will take the .1?
-Original Message-
From: Paul Omamogho [mailto:[email protected]]
Sent: Monday, December 15, 2014 3:30 PM
To: [email protected]
Subject: Re: Proper way to make shared net
On 15/12/2014 6:45 PM, "Jochim, Ingo" wrote:
>
> Hello Lee,
>
> thanks for sharing your ideas.
> In this scenario someone needs to administer the NAS and handle all
requests, right?
Yes, that's correct
>
> In the case you have a little VM which shares the storage then all
traffic will go through
24 matches
Mail list logo
