Re: [smartos-discuss] [smartos-discuss] [smartos-discuss] AMD Ryzen 7 Support

[Daniel Kontsek]

Hi Karthik,

This is actually really interesting. I used to be a huge fan of Gentoo back in 
the days;
drobbins FTW :)
After I switched to enterprise Linux distros I kept portage prefix on my OS X 
for a long time. I have to say that for a developer/unix admin, portage is a 
great package manager on a workstation.
It is good to hear that Gentoo Prefix works in illumos.

Daniel

> On 30 Jul 2017, at 20:30, karthik <longm...@rediffmail.com> wrote:
> 
> Hi Daniel
> 
> Yes one can use other illumos distros which are more suitable for desktops. I 
> use one of them: XStreamOS. I regularly use Xfce,WindowMaker and KDE 3.5 on 
> my /opt/local on XStreamOS. SmartOS is a hypervisor,its best used that way. I 
> have successfully manually bootstrapped upto stage 3 of gentoo prefix on it 
> using the instructions in the below link:
> 
> https://wiki.gentoo.org/wiki/Project:Prefix/Manual_Bootstrap 
> <https://wiki.gentoo.org/wiki/Project:Prefix/Manual_Bootstrap>
> 
> Why gentoo prefix ? This is another source of packages for my desktop, 
> including things like KDE Plasma 5 desktop, which is not present in pkgsrc 
> stable(Its only present in wip, which is an unstable branch).
> 
> The native IPS package set of XStreamOS provides me with 
> Firefox,LibreOffice,Wine,VLC and other essential applications,so I dont miss 
> these in pkgsrc.
> 
> Cheers
> Karthik
> 
> From: "Daniel Kontsek" <dan...@kontsek.sk <mailto:dan...@kontsek.sk>>
> Sent: Fri, 28 Jul 2017 13:17:59
> To: smartos-discuss@lists.smartos.org 
> <mailto:smartos-discuss@lists.smartos.org>
> Subject: Re: [smartos-discuss] [smartos-discuss] AMD Ryzen 7 Support
> 
> Hello,
> 
> technically it is not a problem to install Xorg + some desktop environment on 
> SmartOS (in the global zone).
> 
> We have a SmartOS-based compute node with /opt/local pkgsrc in place (the OS 
> can be optionally installed on hard drive) [1]. We have successfully 
> installed and used a minimal fluxbox, icewm and xfce4 desktop environments.
> However, the quantity and quality of graphical applications in smartos’ 
> pkgsrc is probably low. For example you can install firefox but the binary 
> won’t start.
> 
> To use fluxbox you can just do:
> $ pkgin install modular-xorg-server xf86-input-keyboard xf86-input-mouse 
> xf86-video-vesa xinit xterm fluxbox
> $ cat > ~/.xinitrc << EOF
> #!/usr/bin/bash
> fluxbox
> EOF
> $ startx
> 
> Another cool thing you can do is to create a Linux (K)VM with graphical 
> environment and all your favourite apps on your SmartOS host. Then enable 
> remote X11 connections [2] in the Linux guest and on SmartOS run a X11 
> client: /opt/local/bin/Xorg -query $DESKTOP_IP :1
> It is not an ideal desktop (e.g. you want have access to USB ports in the 
> host), but I can imagine that for doing development in Eclipse it would work. 
> A CentOS 7 image with Gnome is available here: 
> https://images.erigones.org/appliances/contrib-centos7-desktop/ 
> <https://images.erigones.org/appliances/contrib-centos7-desktop/==>
> (KVM will not work on AMD)
> 
> But there are definitely other illumos distributions, which are more suitable 
> for desktops.
> 
> Daniel
> 
> [1] https://wiki.smartos.org/display/DOC/Installing pkgin 
> <https://wiki.smartos.org/display/DOC/Installing+pkgin==>
> [2] 
> https://github.com/erigones/esdc-factory/blob/master/ansible/roles/contrib-centos7-desktop/tasks/main.yml#L57
>  
> <https://github.com/erigones/esdc-factory/blob/master/ansible/roles/contrib-centos7-desktop/tasks/main.yml#L57==>
> 
> > On 27 Jul 2017, at 20:27, a b <tripivc...@hotmail.com> wrote:
> >
> >> Can SmartOS  be  used  at  all  as  a  workstation  for  web  app
> >> development,say  for  java/php development with Eclipse? AFAIK we
> >> can use it as a live image booted off CD/USB with  everything  in
> >> memory,  except for /opt . This is akin to a liveCD of linux like
> >> Knoppix. I do some of my personal web development on illumos  but
> >> I  use  XStreamOS  which has a desktop version. So for XStreamOS,
> >> apart from the native IPS package set, I have options of Joyent's
> >> pkgsrc,OpenCSW or gentoo prefix as package sets.
> >
> > Unfortunately not, as SmartOS is a  hypervisor  most  similar  to
> > VMware ESXi.
> >
> > What you could do is run a joyent-branded zone inside of  SmartOS
> > with X libraries and one of the X window managers, but you'd need
> > an X server to bring the display back to, defeating  the  purpose
> > of running SmartOS as a desktop, since you'd need another desktop
> > to do that.
> >
> > You can

[smartos-discuss] Contributing to smartos-live

[Daniel Kontsek]

Dear Joyent and SmartOS Community,

we have been successfully using and integrating SmartOS at Danube Cloud 
(Erigones) for about 5 years now. At the beginning we've built an IaaS 
platform, which we've transformed into a full-featured software solution - 
Danube Cloud (former Erigones SDDC) [1]. During this time, there were 
occasional moments where we thought that a Linux hypervisor would maybe be a 
better choice... But the strengths of SmartOS / illumos gave ourselves 
repeatedly arguments that - YES - it was the right choice (Zones, ZFS, 
Crossbow, DTrace... you know the perks...). We would like to say to all illumos 
and SmartOS contributors: THANK YOU for the amazing work.

Although, we would like to use the SmartOS platform as it is, we have to 
maintain some changes to the illumos-joyent and smartos-live repositories. This 
is mostly because of support for installation/boot from hard drive (contributed 
by Juraj Lutter), installer (prompt-config) script location and other smaller 
changes to the installer. As far as my understanding goes, Joyent would not 
want to support installation to hard drive but maybe some other (smaller) 
features would be beneficial for Joyent and the SmartOS community. We can 
create pull requests for that, but there are a few topics I would like to 
discuss first:

- AFAIK we should open merge requests here: https://cr.joyent.us/ and not on 
GitHub, but we should create an issue on GitHub first, is this correct, or can 
we just create CRs in Gerrit?

- Shell scripts coding style (mainly svc/methods and prompt_config) is a 
problem. We are seeing mixing of bash coding patterns, even in scripts where 
new bash features are used. (e.g. $var vs ${var} vs "${var}", `` vs $(), [ vs 
[[). I assume lots of these are just Solaris heritage, but some scripts are new 
and yet we see these strange inconsistencies. I'm not going to argue about line 
length and tabs vs spaces (although please don't mix them). But as we are 
saying: at least do it consistently wrong :) We are happily using shellcheck 
[2] for most of our bash scripts and it does solve these kind of problems. Is 
there a coding style guide for shell scripts?

- For example: we would love to rewrite the smartos_prompt_config.sh script so 
it does not use global variables. Would you accept such change?

Daniel


[1] https://github.com/erigones/esdc-ce/wiki
[2] https://github.com/koalaman/shellcheck


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Contributing to smartos-live

[Daniel Kontsek]

Thank you very much Cody for pointing me in the right direction.

I already went ahead and followed the Gerrit instructions and created a CR: 
https://cr.joyent.us/#/c/2353/ <https://cr.joyent.us/#/c/2353/> I did this to 
learn the process of working with Gerrit (not that the bug/CR itself isn’t 
important - it is). The workflow is different compared to the GitHub/GitLab 
(forks/branches) style. I’ve accidentally created and abandoned another CR when 
pushing an update to gerrit - sorry for that. Then I followed the Gerrit 
documentation to update the CR and I’ve just noticed the "We have one major 
exception to the standard Gerrit workflow:…” message in the wiki. I’ve used the 
“amend + Change-Id” method to add another patchset and again: I’m sorry for 
that (I didn’t notice it the first time).

Should I abandon the Change 2353 and create a new one?

Daniel

> On 17 Aug 2017, at 20:51, Cody Mello <mel...@joyent.com> wrote:
> 
> Hi Daniel,
> 
> On Wed, Aug 9, 2017 at 12:33 AM, Daniel Kontsek <dan...@kontsek.sk> wrote:
>> AFAIK we should open merge requests here: https://cr.joyent.us/ and not on
>> GitHub, but we should create an issue on GitHub first, is this correct, or 
>> can
>> we just create CRs in Gerrit?
> 
> Yes, merge requests should go through Gerrit for code review. You can
> find instructions on how to get started using Gerrit here:
> 
> https://github.com/joyent/joyent-gerrit/tree/master/docs/user
> 
> You should create an issue on GitHub under the appropriate repository,
> and then reference it in the commit message. For example, something
> like:
> 
> joyent/smartos-live#12345 This Is The Issue's Subject Line
> Reviewed by: Joe Smith <joe.sm...@joyent.com>
> Approved by: Jane Doe <jane@joyent.com>
> 
> If you know of an open Joyent JIRA ticket (you can see them at
> http://smartos.org/bugview/) then you're welcome to reference that in
> the commit message instead.
> 
> Once you have a change on Gerrit, you can ping people in #smartos or
> the Github ticket about it to find reviewers.
> 
>> Shell scripts coding style (mainly svc/methods and prompt_config) is a
>> problem. We are seeing mixing of bash coding patterns, even in scripts where
>> new bash features are used. (e.g. $var vs ${var} vs "${var}", `` vs $(), [ vs
>> [[). I assume lots of these are just Solaris heritage, but some scripts are
>> new and yet we see these strange inconsistencies. I'm not going to argue 
>> about
>> line length and tabs vs spaces (although please don't mix them). But as we 
>> are
>> saying: at least do it consistently wrong :) We are happily using shellcheck
>> [2] for most of our bash scripts and it does solve these kind of problems. Is
>> there a coding style guide for shell scripts?
> 
> This is the bash style guide, but it could definitely do with some
> additional recommendations:
> 
> https://github.com/joyent/eng/blob/master/docs/index.md#bash-programming-guidelines
> 
> Dave Eddy at Joyent wrote some personal recommendations for writing
> shell scripts, many of which should probably also be in the guide:
> 
> http://daveeddy.com/bash/
> 
> A lot of the scripts in smartos-live have vastly different styles. If
> you're making changes in an area where someone has diverged from the
> prevailing style of the file, then please do update that region to
> match, so that over time each file can at least become consistent with
> itself. In the long run, I'd like to flesh out the style guide and
> write a linter/style checker to help enforce the guidelines.
> 
>> For example: we would love to rewrite the smartos_prompt_config.sh script so
>> it does not use global variables. Would you accept such change?
> 
> smartos_prompt_config.sh could definitely do with some love. If you
> can clean it up to be more readable and safer, we'd probably take
> those changes. Just please make sure to also do testing for all of the
> paths you change, and attach testing notes to the Github issue.
> 
> -  Cody
> 


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] NIC name problem after cloud-init update

[Daniel Kontsek]

Hello SmartOS users,

We’ve encountered a problem, where NICs inside a guest KVM OS got renamed after 
a system update.

We are using RHEL/CentOS VMs and also provide some CentOS images. The recent 
7.4 (1708) release of RHEL/CentOS includes an updated version of the cloud-init 
package, which renames NICs according to the nics.*.interface property, which 
is all right. However, the previous version of RHEL/CentOS included cloud-init 
0.7.5 (officially released 2014-04-01), which ignored the nics.*.interface 
property and NICs were named eth. The latest version of RHEL/CentOS has 
cloud-init 0.7.9 (released 2016-12-23). The SmartOS-related change happened in 
version 0.7.7 (released 2016-08-10).

For all Danube Cloud users - the problem and fix is described here: 
https://github.com/erigones/esdc-ce/wiki/Known-Issues#network-down-in-vms-after-update-of-cloud-init-or-centos
 

 We are sorry for any troubles caused by this issue.

Daniel


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] OT: Danube Cloud is looking for partners

[Daniel Kontsek]

Hi,

I want to address this to all SmartOS users out there, so I believe this is the 
right channel.

At Danube Cloud we have created an open source cloud management software on top 
of SmartOS and are currently looking for strategic partners, especially in the 
US region. We can offer exclusivity, technical expertise and are open to any 
business discussions. For more info check out this blog post: 
https://danubecloud.com/join-us/ 

Daniel


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] No resolv.conf in ubuntu-certified-17.10

[Daniel Kontsek]

Hello,

We’ve got a bug report  about 
the ubuntu-certified-17.10 

 image from images.joyent.com  not setting 
/etc/resolv.conf from the resolvers property in vmadm. The 
ubuntu-certified-16.04 image and other ubuntu-certified images before set 
/etc/resolv.conf correctly.

At first, I was thinking that this has something to do with cloud-init. But 
after playing around I noticed that the resolvconf package is missing or was 
removed as there is a symlink to a non-existent file in /run (/etc/resolv.conf 
-> ../run/resolvconf/resolv.conf). Installing resolvconf solves the problem.
However, there is also the systemd-resolved service, which maintains 
/run/systemd/resolve/resolv.conf from the first boot. So changing the symlink 
to point to /run/systemd/resolve/resolv.conf seems to be the best solution.

Daniel


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Create network overlays after boot

[Daniel Kontsek]

Hi,

This post can be considered as continuation of
https://www.mail-archive.com/smartos-discuss@lists.smartos.org/msg04922.html 


Overlay networking in SmartOS is great but the inability to configure them 
automatically after boot is a real PITA. We have a proposal of implementation 
of overlays persistence using the config file. But before  we implement it, I 
want to ask the community - maybe there's already some other way planned for 
overlay persistence.

The proposal is described here: 
https://github.com/erigones/esdc-factory/issues/85#issuecomment-340701358 


Basically, the `overlay_="”` from usbkey/config will be 
transformed into a valid json in /var/run/smartdc/networking/overlay_rules.json 
by network/physical SVC.

Daniel


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Create network overlays after boot

[Daniel Kontsek]

Hi Robert, Cody et al.

Finally, we have released a version of Danube Cloud that is able to use network 
overlays. And together with IPSec there is now a way to control “remote nodes” 
in other physical datacenters (without the need of a dedicated L2 link). We are 
using the file search plugin and Danube Cloud makes sure the “arp table files” 
are correctly distributed across nodes.

I have to say that overlay networking is a very nice piece of technology. 
Especially, I like the possibility of having different search plugins. Thank 
you for that.

For overlays to work, we've made the decision to include a new service into the 
platform - network/virtual, which took over some responsibilities from 
network/physical. It can create overlay rules, overlays, etherstubs and vNICs. 
The idea and the usbkey/config syntax for overlays is explained in the method 
comments: 
https://github.com/erigones/esdc-erigonos-overlay/blob/master/lib/svc/method/net-virtual#L30
 
<https://github.com/erigones/esdc-erigonos-overlay/blob/master/lib/svc/method/net-virtual#L30>
We’ve tried to implement it in a backward compatible way. Currently the service 
is able to create newly configured vNICs via SMF refresh (without reboot). We 
didn’t change nictagadm, although it would be probably the next logical step.
We think that SmartOS users would benefit from a unified network configuration 
of overlays, etherstubs, and vNICs; What would it take to get it into vanilla 
SmartOS?

For SmartOS users we wrote some basic documentation about overlays and IPSec:
https://github.com/erigones/esdc-ce/wiki/SmartOS-Overlays 
<https://github.com/erigones/esdc-ce/wiki/SmartOS-Overlays>
https://github.com/erigones/esdc-ce/wiki/Enabling-IPSec-on-SmartOS 
<https://github.com/erigones/esdc-ce/wiki/Enabling-IPSec-on-SmartOS>

There is even more documentation in our user guide, e.g.: 
https://docs.danubecloud.org/user-guide/network/overlays.html 
<https://docs.danubecloud.org/user-guide/network/overlays.html> The IPSec 
troubleshooting guide 
https://docs.danubecloud.org/user-guide/network/debug-ipsec.html 
<https://docs.danubecloud.org/user-guide/network/debug-ipsec.html> is also 
something that a SmartOS user can make use of.

Daniel

> On 29 Nov 2017, at 01:18, Robert Mustacchi <r...@joyent.com> wrote:
> 
> On 10/31/17 2:16 , Daniel Kontsek wrote:
>> Hi,
>> 
>> This post can be considered as continuation of
>> https://www.mail-archive.com/smartos-discuss@lists.smartos.org/msg04922.html 
>> <https://www.mail-archive.com/smartos-discuss@lists.smartos.org/msg04922.html>
>> 
>> Overlay networking in SmartOS is great but the inability to configure them 
>> automatically after boot is a real PITA. We have a proposal of 
>> implementation of overlays persistence using the config file. But before  we 
>> implement it, I want to ask the community - maybe there's already some other 
>> way planned for overlay persistence.
> 
> Hi Daniel,
> 
> Thanks for putting this together. Sorry it's taken a while to get back
> around to this. When I put together the overlay stuff originally I
> wasn't sure how we wanted to expose it and have it make sense.
> 
>> The proposal is described here: 
>> https://github.com/erigones/esdc-factory/issues/85#issuecomment-340701358 
>> <https://github.com/erigones/esdc-factory/issues/85#issuecomment-340701358>
>> 
>> Basically, the `overlay_="”` from usbkey/config will 
>> be transformed into a valid json in 
>> /var/run/smartdc/networking/overlay_rules.json by network/physical SVC.
> 
> One thing that we've been trying to do with the nic tags and really this
> is just another form of it is to have this be managed by nictagadm. I
> think the config logic is probably alright, but I'd want to make sure
> that we're able to manage it that way and have using nictagadm really be
> the interface for this rather than having folks continue using the tag.
> 
> Cody, what do you think here?
> 
> Robert
> 


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

[smartos-discuss] Python psycopg2 issue

[Daniel Kontsek]

Hello everyone,

We are deploying a lot of Python software on SmartOS zones and since we are 
also using Postgres, we need the psycopg2 Python module. Recently, I came a 
across an issue with the latest version of psycopg2 which now, can not be 
compiled on SmartOS: https://github.com/psycopg/psycopg2/issues/677 


It turns out that this happened because of a patch that _added_ support for 
Solaris 10 (https://github.com/psycopg/psycopg2/pull/606 
). I’m not that good in C, but 
maybe someone here can propose a (simple?) fix for this issue (or point me to 
some macro or something…).

Thanks,

Daniel


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Re: [smartos-discuss] Python psycopg2 issue

[Daniel Kontsek]

That was quick :) Thank you guys.

Daniel

> On 16 Feb 2018, at 23:40, Mike Gerdts <mike.ger...@joyent.com> wrote:
> 
> An untested fix is at:
> 
> https://github.com/mgerdts/psycopg2/commit/eb711c78d71384600113d549ec6714aa079928a3
>  
> <https://github.com/mgerdts/psycopg2/commit/eb711c78d71384600113d549ec6714aa079928a3>
> 
> It builds on SmartOS.  I've not built it on Solaris 10 or run it anywhere.
> 
> MIke
> 
> On Fri, Feb 16, 2018 at 4:09 PM, Daniel Kontsek <dan...@kontsek.sk 
> <mailto:dan...@kontsek.sk>> wrote:
> Hello everyone,
> 
> We are deploying a lot of Python software on SmartOS zones and since we are 
> also using Postgres, we need the psycopg2 Python module. Recently, I came a 
> across an issue with the latest version of psycopg2 which now, can not be 
> compiled on SmartOS: https://github.com/psycopg/psycopg2/issues/677 
> <https://github.com/psycopg/psycopg2/issues/677>
> 
> It turns out that this happened because of a patch that _added_ support for 
> Solaris 10 (https://github.com/psycopg/psycopg2/pull/606 
> <https://github.com/psycopg/psycopg2/pull/606>). I’m not that good in C, but 
> maybe someone here can propose a (simple?) fix for this issue (or point me to 
> some macro or something…).
> 
> Thanks,
> 
> Daniel
> 
> smartos-discuss | Archives 
> <https://www.listbox.com/member/archive/184463/=now>  
> <https://www.listbox.com/member/archive/rss/184463/25781774-03b23c43> | 
> Modify <https://www.listbox.com/member/?;> Your Subscription   
> <http://www.listbox.com/>


signature.asc
Description: Message signed with OpenPGP




---
smartos-discuss
Archives: https://www.listbox.com/member/archive/184463/=now
RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=25769125_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com