On 2019-12-30 12:47:21 +0100 (+0100), Thomas Goirand wrote:
[...]
> Thinking that there's only VMs is a dangerous assumption. There's also
> bare-metal with Ironic. In such environment, it wouldn't be surprising
> to have VLAN and bonding, then the user may need bridging.
[...]
There are plenty
On Tue, 31. Dez. 2019 at 10:36 Uhr Thomas Goirand wrote:
> > I disagree with that. As mentioned several times, this is not about
> > constructing the /etc/network/interfaces manually but cloud-init (as
> > provided by the cloud image!) behavior, writing the network
> > configuration based on
On 12/30/19 3:53 AM, Noah Meyerhans wrote:
> Unfortunately, AFAICT, ifupdown is also pretty much dead. It hasn't
> seen any major feature development in quite some time, and hasn't seen
> an upload to unstable in nearly a year.
There's at least ifupdown2 from Cumulus (also in Debian) that
On 12/30/19 3:26 PM, Christian Tramnitz wrote:
> On Mo., 30. Dez. 2019 at 03:53 Uhr Noah Meyerhans wrote:
>
>> I agree that current support is not perfect, but I don't think there's
>> any reason for our users to feel blocked by this lack of support.
>> 100% of expected functionality is
On Mo., 30. Dez. 2019 at 03:53 Uhr Noah Meyerhans wrote:
> I agree that current support is not perfect, but I don't think there's
> any reason for our users to feel blocked by this lack of support.
> 100% of expected functionality is available.
I disagree with that. As mentioned several times,
On 12/30/19 1:53 AM, Ross Vandegrift wrote:
> On Sun, Dec 29, 2019 at 11:16:20PM +0100, Thomas Goirand wrote:
>> It isn't uncommon to have a vlan on top of a bridge, on top of a bond
>> (in fact, that's very common for OpenStack), and in this type of setup,
>> not having the ifenslave + vlan +
On Sun, Dec 29, 2019 at 11:16:20PM +0100, Thomas Goirand wrote:
> >> Right, both bridge-utils and vlan are required to setup a bridge or
> >> vlan from *within* /etc/network/interfaces.
> >
> > That's not really true. bridge-utils and vlan add some additional
> > syntax, but everything can be
On Sun, Dec 29, 2019 at 11:16:20PM +0100, Thomas Goirand wrote:
> It isn't uncommon to have a vlan on top of a bridge, on top of a bond
> (in fact, that's very common for OpenStack), and in this type of setup,
> not having the ifenslave + vlan + bridge-utils packages would be a real
> pain.
Is it
On 12/28/19 7:27 PM, Noah Meyerhans wrote:
> On Fri, Dec 27, 2019 at 10:33:16PM +0100, Christian Tramnitz wrote:
>> Right, both bridge-utils and vlan are required to setup a bridge or
>> vlan from *within* /etc/network/interfaces.
>
> That's not really true. bridge-utils and vlan add some
On Sa., 28. Dez. 2019 at 19:20 Uhr Noah Meyerhans wrote:
>
> On Sat, Dec 28, 2019 at 12:23:04PM +0100, Christian Tramnitz wrote:
> > There is no workaround for the lack of vlan and bridge-utils though.
> > It would be great it we could get those two included into the base
> > image.
>
> Both vlan
On Fri, Dec 27, 2019 at 10:33:16PM +0100, Christian Tramnitz wrote:
> Right, both bridge-utils and vlan are required to setup a bridge or
> vlan from *within* /etc/network/interfaces.
That's not really true. bridge-utils and vlan add some additional
syntax, but everything can be accomplished
On Sat, Dec 28, 2019 at 12:23:04PM +0100, Christian Tramnitz wrote:
> There is no workaround for the lack of vlan and bridge-utils though.
> It would be great it we could get those two included into the base
> image.
Both vlan and bridge-utils are legacy tools that are replaced by ip(8)
on modern
On Fr., 27. Dez. 2019 at 23:46 Uhr Noah Meyerhans wrote:
> Yes, but the workaround I provided completely replaces the missing
> functionality. IMO if the docs described the process in the workaround,
> rather than the existing behavior based on apt-key, we'd be done.
I think the workaround is
On Fri, Dec 27, 2019 at 11:39:00PM +0100, Thomas Goirand wrote:
> >> it is virtually impossible to use the image for cloud-init based
> >> deployment:
> >> While cloud-init can also install missing packages, the install would
> >> happen *after* package installation and network setup.
On 12/27/19 10:25 PM, Noah Meyerhans wrote:
> On Fri, Dec 27, 2019 at 02:16:05PM +0100, Christian Tramnitz wrote:
>> However, I'm running into multiple problems staging a system through
>> cloud-init.
>> Without the packages
>> - bridge-utils
>> - vlan
>> - gnupg2
>> it is virtually impossible to
Am Fr., 27. Dez. 2019 um 22:04 Uhr schrieb Thomas Goirand :
> Probably the ip command can be used to setup vlan, though to my
> understanding, the vlan package is needed for ifupdown to understand
> interfaces of type vlan, and the same way, bridge-utils is needed
> for bridges, and ifenslave for
On Fri, Dec 27, 2019 at 02:16:05PM +0100, Christian Tramnitz wrote:
> However, I'm running into multiple problems staging a system through
> cloud-init.
> Without the packages
> - bridge-utils
> - vlan
> - gnupg2
> it is virtually impossible to use the image for cloud-init based deployment:
>
On 12/27/19 9:15 PM, Geert Stappers wrote:
> On Fri, Dec 27, 2019 at 02:16:05PM +0100, Christian Tramnitz wrote:
>> I'm trying to use the Buster generic image
>> (https://cdimage.debian.org/cdimage/cloud/buster/20191117-80/debian-10-generic-amd64-20191117-80.qcow2)
>> to automate deployment of
On Fri, Dec 27, 2019 at 02:16:05PM +0100, Christian Tramnitz wrote:
> I'm trying to use the Buster generic image
> (https://cdimage.debian.org/cdimage/cloud/buster/20191117-80/debian-10-generic-amd64-20191117-80.qcow2)
> to automate deployment of KVM-based VMs. The reason that I'm not using
> the
I'm trying to use the Buster generic image
(https://cdimage.debian.org/cdimage/cloud/buster/20191117-80/debian-10-generic-amd64-20191117-80.qcow2)
to automate deployment of KVM-based VMs. The reason that I'm not using
the genericcloud or OpenStack image is that I'm passing through
network VFs that
20 matches
Mail list logo
