GitHub user boring-cyborg[bot] added a comment to the discussion: Initial zone
set-up does not verify usable secondary storage - leads to issues
Thanks for opening your first issue here! Be sure to follow the issue template!
GitHub link:
https://github.com/apache/cloudstack/discussions/9036#
GitHub user Jayd603 added a comment to the discussion: Initial zone set-up does
not verify usable secondary storage - leads to issues
> @Jayd603 , can you remove the zone/storage and re-add instead?
It takes a lot of steps to delete a zone and I don't remember if it removed the
stale/bad seco
GitHub user Jayd603 added a comment to the discussion: Initial zone set-up does
not verify usable secondary storage - leads to issues
> @Jayd603 , is your system vm template seeded on your secondary storage? The
> path `/template/tmpl/1/3` on your secondary storage should contain a valid
> sy
GitHub user DaanHoogland added a comment to the discussion: Initial zone set-up
does not verify usable secondary storage - leads to issues
@Jayd603 , is your system vm template seeded on your secondary storage? The
path `/template/tmpl/1/3` on your secondary storage should contain a valid
sys
GitHub user DaanHoogland added a comment to the discussion: Initial zone set-up
does not verify usable secondary storage - leads to issues
@Jayd603 , can you remove the zone/storage and re-add instead?
GitHub link:
https://github.com/apache/cloudstack/discussions/9036#discussioncomment-930252
Hi everyone.
I have a CloudStack 4.17 cluster x86_64 using KVM/QEMU as a hypervisor.
I've been exploring the possibility of using a Raspberry Pi as a host,
as an alternative to conventional servers. Following the steps of this
tutorial [https://rohityadav.cloud/blog/cloudstack-arm64-kvm], I ma
GitHub user phsm added a comment to the discussion: External DNS servers
provided with use.external.dns disabled
> As a workaround you can configure your internal DNS server as external DNS
> server as well, or not configure an external DNS for this network.
This particular workaround won't w
Hi,
In our current in-home libvirt-based solution, we can spin up instances that
have access to the public network (public IP addresses) and a private VLAN
network on a secondary interface. Am I correct in understanding that it
currently isn't possible to have an advanced private network (isolat
GitHub user hrak added a comment to the discussion: External DNS servers
provided with use.external.dns disabled
Even if this is considered intended behavior, it still seems wrong. Adding
external DNS's that don't know anything about the instances in the isolated
network to the list of resolv
GitHub user DaanHoogland added a comment to the discussion: External DNS
servers provided with use.external.dns disabled
To me it looks like you either want
- an extra setting `use.internal.dns` to be able to switch off the
`` addition.
- an extra setting `bypass.external.dns` to be able to sw
GitHub user kriegsmanj added a comment to the discussion: External DNS servers
provided with use.external.dns disabled
> @kriegsmanj the description of the global setting is: `Bypass internal dns,
> use external dns1 and dns2` it looks like the global setting is used to
> determine if interna
GitHub user weizhouapache added a comment to the discussion: External DNS
servers provided with use.external.dns disabled
> Even if this is considered intended behavior, it still seems wrong. Adding
> external DNS's that don't know anything about the instances in the isolated
> network to the
GitHub user kriegsmanj added a comment to the discussion: External DNS servers
provided with use.external.dns disabled
In case of an isolated network, the resolvers configured are the Virtual Router
IP and external dns1/dns2 in zone setting.
In our environment we have no internal dns1/dns2 co
GitHub user DaanHoogland added a comment to the discussion: External DNS
servers provided with use.external.dns disabled
@kriegsmanj , @hrak , very sorry that it doesn't behave as you would expect,
and we can certainly change it, but we'll have to do that in a backwards
compatible way as it i
GitHub user hrak added a comment to the discussion: External DNS servers
provided with use.external.dns disabled
I think the problem lies in [the logic
here](https://github.com/apache/cloudstack/blob/f41c934c94ad50e0bb3e51c26e52ac78196acd69/server/src/main/java/com/cloud/network/router/Virtual
GitHub user weizhouapache added a comment to the discussion: External DNS
servers provided with use.external.dns disabled
> > @kriegsmanj the description of the global setting is: `Bypass internal dns,
> > use external dns1 and dns2` it looks like the global setting is used to
> > determine i
GitHub user weizhouapache added a comment to the discussion: External DNS
servers provided with use.external.dns disabled
@kriegsmanj
the description of the global setting is: `Bypass internal dns, use external
dns1 and dns2`
it looks like the global setting is used to determine if internal d
GitHub user weizhouapache added a comment to the discussion: External DNS
servers provided with use.external.dns disabled
> In case of an isolated network, the resolvers configured are the Virtual
> Router IP and external dns1/dns2 in zone setting. In our environment we have
> no internal dns
GitHub user boring-cyborg[bot] added a comment to the discussion: Cloustack
agent (4.18.1.0) status stuck on activating
Thanks for opening your first issue here! Be sure to follow the issue template!
GitHub link:
https://github.com/apache/cloudstack/discussions/9028#discussioncomment-9294925
GitHub user weizhouapache added a comment to the discussion: Cloustack agent
(4.18.1.0) status stuck on activating
@Ash6990
Have the bridges (cloudbrX) been configured ?
If not, please refer to the cloudstack document how to setup a kvm host.
GitHub link:
https://github.com/apache/clouds
Hi Hanis,
You can find the removed template URL using the SQL query below, you can
register a new one.
select url from vm_template where type='BUILTIN';
-Jithin
From: Hanis Irfan
Date: Wednesday, 1 May 2024 at 10:39 AM
To: users@cloudstack.apache.org
Subject: RE: Secondary storage system VM
I like the general idea but at the same time want to weight in that we also do
the right thing in handle issues and PRs. Sometimes there are genuine issues
and PRs, however, we make no progress on them for one reason or another.
As of last week, I've triaged all the outstanding Github issues tha
22 matches
Mail list logo
