[02:44] <gtrmtx> hey guys, i have an apache question and #httpd is dead at the moment. mind if i ask here?
[02:45] <sarnold> sure
[02:45] <sarnold> it's pretty dead here too though :/ hehe
[02:45] <gtrmtx> lol i hear ya
[02:45] <gtrmtx> friday night
[02:45] <gtrmtx> this is my setup
[02:45] <gtrmtx> http://pasteall.org/pic/show.php?id=8799afe9f3ad11a8fefb7c702bff54e9
[02:45] <sarnold> yah. It's just about the end of my attention span, hehe :)
[02:46] <gtrmtx> the problem is site2 is trying to resolve the private ip on the client side
[02:47] <sarnold> which process is doing the resolving?
[02:48] <gtrmtx> what do you mean?
[02:48] <gtrmtx> thats if i type sub.domain.com in the browser
[02:50] <sarnold> you can use dnsviz to get an independent view of what your DNS servers are serving .. http://dnsviz.net/d/www.gmail.com/dnssec/
[12:37] <RoyK> what happened to lvm in the 18.04 server installer?
[12:37] <RoyK> or raid?
[13:12] <tomreyn> hmm, good point, it doesn't seem to support lvm or raid or FDE (yet?).
[13:13] <tomreyn> that's if we'Re talking the "live" installer
[13:13] <tomreyn> i think the old one still does
[13:13] <tomreyn> the "live" one also seem to fail to detect existing partitions
[13:14] <tomreyn> that's my local copy  of the daily build form apr 5
[13:22] <RoyK> FDE?
[13:23] <RoyK> tomreyn: yes, I was thinking of the "live" installer - is there a boot argument or anything to use the old one instead? the new one doesn't seem complete, or perhaps just a nice thing for newbies
[13:23] <RoyK> oh - fde - encryption - sorry
[13:24] <tomreyn> FDE -> full disk encryption (dymcrypt-LUKS)
[13:24] <RoyK> yeah, googled it ;)
[13:24] <RoyK> just hadn't seen that acronym before
[13:25] <tomreyn> i dont actually know but i'd be surprised if the server 'live' installer could switch to the old installer using a boot parameter. i think you will need to download a daily build or beta of the classic installer instead
[13:27] <tomreyn> i seriously hope the serve 'live' installer won't be considered the default media for server installations before this functionality is added.
[13:28] <RoyK> it's the default on the beta
[13:28] <tomreyn> TJ-: any idea how to get the right people's attention on this?
[13:29] <RoyK> http://releases.ubuntu.com/18.04/ <-- nothing but the "live" installer there for server
[13:29] <tomreyn> right
[13:30] <tomreyn> non "live" server installers for beta2 are at http://cdimage.ubuntu.com/releases/18.04/beta-2/
[13:31] <tomreyn> daily: http://cdimage.ubuntu.com/ubuntu-server/daily/
[13:31] <tomreyn> daily live: http://cdimage.ubuntu.com/ubuntu-server/daily-live/
[13:33] <TJ-> tomreyn: sounds like typical Canonical, throw it out before it has feature parity. The whole idea of a 'live' server install makes little sense - from what I've heard it's like netplan.io - missing core features and seemingly not being actively enhanced (at least not rapidly enough to not cause a lot of pain)
[13:34] <tomreyn> yes :-/ more dev than ops
[13:35] <RoyK> I can see the point of a live installer - it gives you a *lot* of control and tools in case of fixing a broken system - but then - it doesn't make sense if the installer can't do the same as (or more than) the old one
[13:35] <tomreyn> i do like the new live installers' interface, though, but without supporting these critical functionalities, it's just not ready.
[13:35] <RoyK> indeed
[13:36] <TJ-> less bling, more bang!
[13:36] <RoyK> and now it's past feature freeze, so I guess it'll stay
[13:37] <TJ-> look at the massive numbers of enhancements/bugs in the Canonical projects and you see the same theme. netplan.io, gnome-software (ubuntu-software), subiquity, etc.
[13:37] <tomreyn> i guess preseeding works differently for live and non live also. if so, then companies will hate to switchto live and later back to classic server installer.
[13:40] <tomreyn> i can understand the commercial drive to create something ubuntu-unique, pseudo (or really?) proprietary to create a(nother?) USP, but i wish this was created a different way.
[13:40] <TJ-> well preseed is handled by debian-installer. not sure subiquity is designed to do that. From what I read it's more about 'dd'-ing prepared images into place
[13:40] <tomreyn> on the other hand canonical seems to struggle a lot financially, setting off employees and killing projects regularly.
[13:42] <tomreyn> https://wiki.ubuntu.com/UbiquityAutomation
[13:42] <tomreyn> last edited 2015-03-24
[13:43] <tomreyn> "Preseeding keys for the following installer components will not be used in Ubiquity, usually because they do not fit with Ubiquity's mode of operation: [...] LVM and RAID partitioning [...]"
[13:43] <TJ-> tomreyn: Canonical is trying to prepare itself to get additional outside investment, which requires each project/unit/team to be profitable
[13:44] <TJ-> Hence dropping Mir, Unity, and so forth
[13:44] <tomreyn> i understand that killing non profitable projects makes complete sense economically and is actually a requirement for a healthy business.
[13:44] <TJ-> Yes... the issue though is they throw these projects out into the path of everyone then leave them half-finished or buggy.
[13:45] <tomreyn> right
[13:46] <TJ-> Until they started this subiquity project I had thought -server would remain safe in the main, even though there's a lot of Canonical stuff going around it like Openstack, MAAS, Landscape, the LXC>LXD containers
[13:46] <tomreyn> is "subiquity" not a typo then?
[13:46] <tomreyn> i thought you meant "ubiquity"
[13:47] <TJ-> not at all (Server Ubiquity) although from what I've seen it doesn't build on ubiquity, it's a totally separate project
[13:47] <tomreyn> got it
[13:47] <TJ-> !info subiquity
[13:47] <RoyK> what's Mir?
[13:47] <tomreyn> oh ok
[13:47] <TJ-> RoyK: it was Caonical's display server supposed to compete with Wayland protocol compositors
[13:48] <RoyK> oh
[13:48] <RoyK> well, guess I'll stick to Debian, then, if these are the ways of Canonical
[13:49] <TJ-> tomreyn: well, finally got an 18.04 charoot doing 12.04 > debootstrap > 16.04 > debootstrap >18.04 !
[13:49] <tomreyn> wohoo!
[13:50] <TJ-> RoyK: the core desktop has dropped Unity and has returned to Gnome, adopted Wayland where it's viable but sticking with Xorg as the default now (since gnome-mutter (Wayland compositor) still has a lot of deficiences
[13:50] <tomreyn> btw there is https://github.com/CanonicalLtd/subiquity/blob/master/subiquity/models/raid.py
[13:50] <tomreyn> but i didnt see how to use it on the UI
[13:50] <TJ-> tomreyn: best to stick to Debian-Installer - it has 20 years of experience of doing these things!
[13:51] <tomreyn> yes, manual partitioning makes me want to do things to who invented it, though
[13:51] <tomreyn> but we can preseed
[13:51] <tomreyn> and pre-configure partitions
[13:52] <tomreyn> s/invented/implemented/
[13:53] <tomreyn> i guess sdebian installer is the new mini.iso then ;-)
[13:53] <tomreyn> not officially supported but actually required and supported forever.
[13:53] <TJ-> that's down to 'partman' - awful bit of software that is, always rescanning when it's not necessary
[13:53] <tomreyn> err built, not supported
[13:54] <tomreyn> i never used partman outside of the installer, but use parted, an di think both use libparted?
[13:54] <TJ-> right - I have a washing machine bearing to change! Now 18.04 has installed I can come back and port the config over later :)
[13:55] <tomreyn> pregress! stone -> wheel
[13:56] <RoyK> TJ-: I noticed the Xorg rollback
[18:01] <albech> we are in the process of researching alternatives to our Xenserver 7.2 setup, since they have changed the pricing policy in 7.3. We are currently looking into oVirt and Proxmox any other recommendations or comments? Less than 100 nodes and 400 VMs. All SAN storage. Will be setting up a lab environment next week.
[18:04] <albech> We are NOT looking to make it more complicated than need be (KISS). So Openstack has been rules out unless we come up with a REALLY good reason to use it.
[18:23] <AJ2> Hi all
[18:23] <AJ2>  Hi All.  I need some help with my Ubuntu 16.04.  On my network all my devices have an IP as 192.168.1.xxx, but for some reason the IP on my Ubuntu server is 192.168.10.x.  Due to this reason I am not able to ssh into theis machien from the same network and moreoever from outside my home network. In my router settings I do not even see this ubuntu pc; therefore I can safely say I have not assigned a static IP to this machine on my
[18:23] <AJ2> router.
[18:24] <AJ2> I would appreciate anyones help on this.  This is a new install of ubuntu I did
[19:16] <dpb1> albech: Canonical's bootstack might interest you.  https://www.ubuntu.com/cloud/managed-cloud  -- for a straightup xenserver replacement, I mean, it's vsphere, but I can't imagine price there is better. :)  All the features of public cloud are why you use openstack (developer self-service, standard instance launch models, staging -> production workflows, etc).
[19:17] <dpb1> AJ2: are you on the terminal of the Ubuntu server?  do `ip addr; cat /etc/network/interfaces` and pastebin the results please.
[19:18] <dpb1> !pastebin | AJ2
[19:18] <dpb1> !pastebinit | AJ2
[21:39] <RoyK> You are correct that the new live installer does not have feature parity with the existing installer. Replacing something that was developed for more than a decade will take time.
[21:40] <RoyK> The Answer To Why RAID And LVM And FDE Is Not Supported In The Live Install
[21:40] <RoyK> ye gods - replacing a good installer with crap without implementing these things doesn't seem like a very good idea
[22:46] <arooni> not sure why even though i have 3306                       ALLOW       192.168.1.100;;; i dont seem; allowed to telnet from that ip address