kikoreis

41 ms·

181.
by kikoreis 10y ago
Is that completely accurate? As Moxie explained elsewhere they do sync contacts, but that's optional. I'm not sure there's any other dependency beyond the GCM push, which I don't know is very concerning. Google definitel
182.
by kikoreis 10y ago
Unless there is core-specific RAM on the die, why? Isn't the essential aspect of NUMA the fact that there is some memory which is "near", and some which is "far"?
183.
by kikoreis 10y ago
This isn't a very credible counter; being locked in because it was cheap to get hooked is exactly how we got ourselves into our previous disasters. In fact, until open source we kind of stumbled from one into the other. As for comparin
184.
by kikoreis 10y ago
Well, our maintainers (primarily Matthias) package both for Debian and Ubuntu, so they diverge only in the sense that the cadences and versioning are not completely aligned. But regardless of the packaging effort, the real overhead is track
185.
by kikoreis 10y ago
Hah, that's a trick question. Probably for less, given how deeply Debian tooling depends on perl5.
186.
by kikoreis 10y ago
More explicitly, a standard installation of Ubuntu only depends on (and leaves installed) Python 3: $ lxc launch ubuntu:16.10 yakkety [...] $ lxc exec yakkety python || echo no py2 no py2 Python 2 is still available via a
187.
by kikoreis 10y ago
Also, we (Ubuntu) definitely won't maintain or ship Python 2.7 indefinitely; I'm keeping a keen eye on how the ecosystem moves to decide when that happens.
188.
by kikoreis 10y ago
That's a high-risk approach, because big referendums have a lot of downsides. They are expensive, polarizing and put a lot of responsibility on the average citizen, who is expected to both understand and balance correctly the tradeoffs
189.
by kikoreis 10y ago
Hey, Ubuntu/Debian contributor here. Actually, 99% is misrepresenting it. Any [well-packaged] service upgraded through unattended-upgrades (nginx included) gets restarted through package hooks. What unattended-upgrades won't help
190.
by kikoreis 10y ago
Actually, it is installed and enabled by default as of 16.04 LTS; see https://wiki.ubuntu.com/Security/Features for the detail.
191.
by kikoreis 10y ago
Yeah, it's certainly true that the existing SoC product plans were canned. But a lot will need to happen before Intel comes to the point of reevaluating its x86 ISA platform strategy.
192.
by kikoreis 10y ago
Actually, this announcement is about licensing ARM's physical IP to enable the Intel foundries to fab ARM SoCs for other companies, not about Intel building its own ARM SoCs. I'm pretty sure their long bet on x86 SoCs remains unch
193.
by kikoreis 12y ago
Is there a latency angle to webserver performance that /is/ valid? I have heard anecdotal information that single-thread performance does affect webserver response latency and I can see how an optimized server could make a differe
194.
by kikoreis 12y ago
That comment is a bit harsh; I'm sure Ubuntu is pretty relevant regardless of MAAS. For instance, it's the #1 OS deployed as cloud guests anywhere, and it's the #3 desktop OS in the world. But you do raise an interesting poin
195.
by kikoreis 12y ago
All of Amazon's EC2 compute instances are run on top of Xen; there is an interesting Reddit AMA post with a lot of detail: http://www.reddit.com/r/IAmA/comments/1e5o4p/iaman_exaws_eng...
196.
by kikoreis 12y ago
Yeah, exactly! That's what we showed off at a lot of recent demos, including during the OpenStack presentation Mark did: https://www.youtube.com/watch?v=YsYdIJrJRLQ
197.
by kikoreis 12y ago
That use case should work very well for a wide variety of hardware (and in fact I use it myself for a 20-node cluster). Issues may arise from networking and BMC unreliability, which the MAAS teams are currently working hard on addressing fo
198.
by kikoreis 12y ago
Thanks for trying; here's a commentary on your points: > * Auto-enrollment of nodes was tough to get working. > * Overlay and config management was weak and better handled by Puppet. Though Juju beans were touted as able to handl