[OmniOS-discuss] Project-FiFo 0.7.0 release

[Heinz Nikolaus Gies]

Good news everyone!

FiFo 0.7.0 is released today! There is a blog post [1] explaining the details 
so I just want to go over the biggest news and keep this short.

* A shiny new UI.
* A complete overhaul of our documentation.
* Historic metrics for the whole cloud with Tachyon and DalmatinerDB.
* Accounting/usage information for VM’s.
* Full support for OAuth2.
* Experimental support for OmniOS. 

If you want to update we’ve a detailed update section in the docs [2].

[1] https://blog.project-fifo.net/the-biggest-news-yet-0-7-0-and-support 

[2] http://docs-new.project-fifo.net/docs/upgrading-fifo 
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] ipadm failing after first zone boot

[Heinz Nikolaus Gies]

> On Jun 10, 2015, at 14:36, Dan McDonald  wrote:
> 
> 
>> On Jun 6, 2015, at 4:45 PM, Heinz Nikolaus Gies  wrote:
>> 
>> I noticed some rather odd behavior, to set up networking I use the following 
>> commands:
>> 
>> [GZ] dladm create-vnic -l bge0 net4 -p allowed-ips=10.0.0.111/32
>> (do zone creation wait until svc has reached 
>> svc:/milestone/sysconfig:default)
> 
> I'm assuming you've done a zone boot at this point as well?  (You don't say 
> it, but "reached milestone/sysconfig" suggests you have.)
Yup zone boot was done, and I waited till the last milestone was reached (I 
forgot that before ;)
> 
>> [NGZ] ipadm create-if net4
>> [NGZ] ipadm create-addr -T static  -a 10.0.0.111/24 net4/v4
>> ipadm: Could not create address: Operation not permitted on from-gz interface
> 
> That *is* really weird.  I'm assuming you can reproduce this bug?
In 100% of the tests I’ve had done yes, if it were a one time thing I’d have 
just doubted myself and wrote it off as me probably having forgotten something.
> 
> Also, have you tried just doing the create-addr w/o the create-if?  I'm 
> pretty sure you can shortcut, and perhaps it works around the not-permitted 
> problem?
That I have not tried but I’ll give it a try, my work around right now is 
actually doing a full re-boot of the zone so it’s not too huge of a problem, 
but it looked like a bug
> 
> Thanks,
> Dan
> 





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] FiFo on OmniOS

[Heinz Nikolaus Gies]

Hi Stevan,
yap I suppose that would be great but I haven’t yet figured out the ipgk build 
system (any help appreciated ;). For now it’s manual compilation on OmniOS (not 
as horrible as it sounds!) or using a SmartOs system with pkgin.

if you want to compile it it’s rather simple actually this is for SmartOS 
https://gist.github.com/Licenser/c0573322309d973c73b1#file-setup-sh 
<https://gist.github.com/Licenser/c0573322309d973c73b1#file-package-sh> the 
main difference will be that you don’t have pkgin but pkg but it should be 
nearly the same (I’d try to look them up but the pkg search is giving 503’s 
here)


Please be aware so that it is in the test branch and highly experimental ;)

Cheers,
Heinz
---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net



> On Jun 8, 2015, at 11:08, qutic development  wrote:
> 
> Hi Heinz,
> 
> On 04.06.2015, at 02:35, Heinz Nikolaus Gies  wrote:
> 
>> some of you might already noticed by some tweets flying around but Dan and 
>> us have started working making OmniOS a possible hypervisor for 
>> Project-FiFo, or if you want to put it the other way around make 
>> Project-FiFo an possible management system for OmniOS.
> 
> Sounds great and I would like to test it. How do I install it on OmniOS? 
> Something like `pkg install project-fifo` would be fine :)
> 
> Best regards
> Stefan



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] ipadm failing after first zone boot

[Heinz Nikolaus Gies]

I noticed some rather odd behavior, to set up networking I use the following 
commands:

[GZ] dladm create-vnic -l bge0 net4 -p allowed-ips=10.0.0.111/32
(do zone creation wait until svc has reached svc:/milestone/sysconfig:default)
[NGZ] ipadm create-if net4
[NGZ] ipadm create-addr -T static  -a 10.0.0.111/24 net4/v4
ipadm: Could not create address: Operation not permitted on from-gz interface

Now thing become rather strange. Next, if I then reboot the zone and execute 
the failed command (create-addr) again it works and persists over reboots, 
however after the first boot it never does. This smells like some kind of bug 
to me.


---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] FiFo on OmniOS

[Heinz Nikolaus Gies]

Hi everyone,
some of you might already noticed by some tweets flying around but Dan and us 
have started working making OmniOS a possible hypervisor for Project-FiFo, or 
if you want to put it the other way around make Project-FiFo an possible 
management system for OmniOS.

We’ve had some great success so far and the feedback to the tweets was 
excitingly positive so it is time to get the community involved! That means the 
lot of you!

I want to give a rough idea of the plan and current state and the pitfalls. 
Given I know FiFo better then OmniOS this is from the point of view of a FiFo 
user, if a point is not clear please let me know and I’ll elaborate


- (nearly) full manageability of zones, create, start, stop, reboot, delete
- support for snapshots
- support for the zone console
- SMF support (starting, stopping, viewing services of a zone)
- ‘FiFo native feel’ (read: it should make little difference weather one 
deployed a ipkg zone or a joyent zone from the workflow)
- metrics and performance graphing

There are some things that are on the ‘nice to have’ list but might not land in 
a first version:

- resizing (changing memory/disk/etc)
- adding/removing nics

And some things that pretty sure will not happen any time soon (due to too much 
difference from the current way it’s done on SmartOS):

- KVM

There are some things that are a bit problematic and will probably work but not 
be exactly the same as they are on SmartOS

- NIC management, SmartOS seems to have some custom code to bring up nics and 
how to handle them so we’ve to be creative here.
- SSH key management in zones, Dan has build libzdoor (used for SSH key 
management in SmartOS) but so far it’s not tested
- packaing chunter (the service running in the GZ) and tachyon-meter (the 
service collecting performance metrics) run flawlessly in the GZ, they are 
packaged as tarballs and can simply be extracted however there are only pkgin 
packages for the other components. They will pretty guaranteed just compile on 
OmniOS given a new enough Erlang version (R17+) exists but there are currently 
no packages provided for that. (read: need to install from source of have a 
SmartOS zone around)
- it does not look we can get the exact same amount of lock in for zones 
(mostly for nic management) so a first release will probably required trusted 
tenants.


What is working so far:

- creating (with resource control but no networking configured, ipadm acts a 
bit freaky for me, probably a local issue)
- starting / shutting down / halting (commands are all issued but zones tend to 
hang in shutting_down for me, probably a local issue)
- metering (at least the hypervisor itself)
- SMF services should be working
- the Zone console should be working


What can you do?

If anyone wants to help, any kind of discussion is great, there are surely 
things we simply missed and having a more diverse group of people pondering the 
problem will make for a better result in the end. There will probably be some 
questions of how to best do things on OmniOS that I would greatly appreciate 
help with figuring out (see problems with ipadm and shutting_down zones). For 
brave soles who want to give the current status a spin be warned it is part of 
the development branch of fifo so things are rather experimental, but, time 
permits, I’ll try to walk anyone interested though setting it up.

---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] I think I broke part of the network stack

[Heinz Nikolaus Gies]

Had to restart to get the system back into working condition, solved the issue 
but probably lost the state that caused it. Sorry
---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net



> On May 30, 2015, at 20:57, Heinz Nikolaus Gies  wrote:
> 
> adding to that the only content of /etc/dladm/*.conf files is
> 
> bge0
> class=int,1;media=int,4;phyinst=int,1;phymaj=int,120;devname=string,bge0;
> net0
> class=int,8;media=int,4;linkover=string,bge0;maddrtype=int,1;vrid=int,0;vraf=int,0;macaddr=string,2:8:20:c0:a7:c0;
> 
> in /etc/dladm/datalink.conf (comments excluded)
> ---
> Cheers,
> Heinz Nikolaus Gies
> he...@licenser.net
> 
> 
> 
>> On May 30, 2015, at 20:55, Heinz Nikolaus Gies  wrote:
>> 
>> Hi,
>> 
>> I got the feeling that I did break part of the networks tack on a server of 
>> mine. The list of commands I executed are attached, right now no diadem 
>> show-* command returns output (return code is still 0). I do suspect that 
>> was caused by adding a vmic with the same name twice but I am not sure and 
>> don’t want to reboot at this point so no evidence is destroyed.
>> 
>> Cheers,
>> Heinz
>> 
>> 397  dladm show-vnic
>> 398  dladm show-vnic -v
>> 399  dladm show-phys
>> 401  man dladm
>> 402  dladm create-vnic -l bge0 net0
>> 403  dladm show-phys
>> 404  dladm show-vnic
>> 405  dladm destroy-vnic -l bge0 net0
>> 406  dladm delete-vnic -l bge0 net0
>> 407  dladm delete-vnic  net0
>> 408  dladm create-vnic -l bge0 net0 -p 
>> zone=2398fe7c-032f-11e5-abb0-b33f9f953915
>> 412  dladm create-vnic -l bge0 net0
>> 416  dladm show-vnic
>> 417  dladm create-vnic -l bge0 net0
>> 419  dladm show-vnic
>> 490  dladm show-vnic
>> 491  dladm show-phys
>> 492  dladm
>> 493  dladm show-phys
>> 494  dladm show-phys -v
>> 495  dladm
>> 496  dladm show-link
>> 497  dladm show-link
>> 499  dladm show-link
>> 
>> ---
>> Cheers,
>> Heinz Nikolaus Gies
>> he...@licenser.net
>> 
>> 
>> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] I think I broke part of the network stack

[Heinz Nikolaus Gies]

adding to that the only content of /etc/dladm/*.conf files is

bge0
class=int,1;media=int,4;phyinst=int,1;phymaj=int,120;devname=string,bge0;
net0
class=int,8;media=int,4;linkover=string,bge0;maddrtype=int,1;vrid=int,0;vraf=int,0;macaddr=string,2:8:20:c0:a7:c0;

in /etc/dladm/datalink.conf (comments excluded)
---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net



> On May 30, 2015, at 20:55, Heinz Nikolaus Gies  wrote:
> 
> Hi,
> 
> I got the feeling that I did break part of the networks tack on a server of 
> mine. The list of commands I executed are attached, right now no diadem 
> show-* command returns output (return code is still 0). I do suspect that was 
> caused by adding a vmic with the same name twice but I am not sure and don’t 
> want to reboot at this point so no evidence is destroyed.
> 
> Cheers,
> Heinz
> 
>  397  dladm show-vnic
>  398  dladm show-vnic -v
>  399  dladm show-phys
>  401  man dladm
>  402  dladm create-vnic -l bge0 net0
>  403  dladm show-phys
>  404  dladm show-vnic
>  405  dladm destroy-vnic -l bge0 net0
>  406  dladm delete-vnic -l bge0 net0
>  407  dladm delete-vnic  net0
>  408  dladm create-vnic -l bge0 net0 -p 
> zone=2398fe7c-032f-11e5-abb0-b33f9f953915
>  412  dladm create-vnic -l bge0 net0
>  416  dladm show-vnic
>  417  dladm create-vnic -l bge0 net0
>  419  dladm show-vnic
>  490  dladm show-vnic
>  491  dladm show-phys
>  492  dladm
>  493  dladm show-phys
>  494  dladm show-phys -v
>  495  dladm
>  496  dladm show-link
>  497  dladm show-link
>  499  dladm show-link
> 
> ---
> Cheers,
> Heinz Nikolaus Gies
> he...@licenser.net
> 
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] I think I broke part of the network stack

[Heinz Nikolaus Gies]

Hi,

I got the feeling that I did break part of the networks tack on a server of 
mine. The list of commands I executed are attached, right now no diadem show-* 
command returns output (return code is still 0). I do suspect that was caused 
by adding a vmic with the same name twice but I am not sure and don’t want to 
reboot at this point so no evidence is destroyed.

Cheers,
Heinz

  397  dladm show-vnic
  398  dladm show-vnic -v
  399  dladm show-phys
  401  man dladm
  402  dladm create-vnic -l bge0 net0
  403  dladm show-phys
  404  dladm show-vnic
  405  dladm destroy-vnic -l bge0 net0
  406  dladm delete-vnic -l bge0 net0
  407  dladm delete-vnic  net0
  408  dladm create-vnic -l bge0 net0 -p 
zone=2398fe7c-032f-11e5-abb0-b33f9f953915
  412  dladm create-vnic -l bge0 net0
  416  dladm show-vnic
  417  dladm create-vnic -l bge0 net0
  419  dladm show-vnic
  490  dladm show-vnic
  491  dladm show-phys
  492  dladm
  493  dladm show-phys
  494  dladm show-phys -v
  495  dladm
  496  dladm show-link
  497  dladm show-link
  499  dladm show-link

---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] zpool list -p

[Heinz Nikolaus Gies]

zpool upgrade -v shows the same version on both systems.

I would suspect that Joyent has modified the zpool utility, but it seems like a 
sensible change.

---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net



> On May 30, 2015, at 19:20, Krzysztof Grzempa  wrote:
> 
> Did you compare ZFS versions on both OS'es ? This might changed over some new 
> version..
> 
> 2015-05-30 17:58 GMT+02:00 Heinz Nikolaus Gies  <mailto:he...@licenser.net>>:
> I was looking at the output of zpool list today, comparing it with what I’d 
> get on SmartOS and noticed that when using the -p flag for parable output the 
> deduplication factor is still presented as a string (or floatish type) 
> instead of a integer vlaue. It seems to me a bit wrong for parable output.
> 
> If there is a reason behind that decision it’s fine and I’ll gladly work 
> around it, but it feels like an oversight.
> 
> 
> Cheers,
> Heinz
> 
> Here a quick glance:
> 
> OmniOS:
> /usr/sbin/zpool list -pH -oname,size,alloc,free,dedup,health
> data7971459301376   6405101887488   1566357413888   1.00x   ONLINE
> rpool   2491081031681215607413761275473617921.00x   ONLINE
> 
> SmartOS:
> list -pH -oname,size,alloc,free,dedup,health
> zones   31997506355251935040512 268040023040100 ONLINE
> ---
> Cheers,
> Heinz Nikolaus Gies
> he...@licenser.net <mailto:he...@licenser.net>
> 
> 
> 
> 
> ___
> OmniOS-discuss mailing list
> OmniOS-discuss@lists.omniti.com <mailto:OmniOS-discuss@lists.omniti.com>
> http://lists.omniti.com/mailman/listinfo/omnios-discuss 
> <http://lists.omniti.com/mailman/listinfo/omnios-discuss>
> 
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] zpool list -p

[Heinz Nikolaus Gies]

I was looking at the output of zpool list today, comparing it with what I’d get 
on SmartOS and noticed that when using the -p flag for parable output the 
deduplication factor is still presented as a string (or floatish type) instead 
of a integer vlaue. It seems to me a bit wrong for parable output.

If there is a reason behind that decision it’s fine and I’ll gladly work around 
it, but it feels like an oversight.


Cheers,
Heinz

Here a quick glance:

OmniOS:
/usr/sbin/zpool list -pH -oname,size,alloc,free,dedup,health
data7971459301376   6405101887488   1566357413888   1.00x   ONLINE
rpool   2491081031681215607413761275473617921.00x   ONLINE

SmartOS:
list -pH -oname,size,alloc,free,dedup,health
zones   31997506355251935040512 268040023040100 ONLINE
---
Cheers,
Heinz Nikolaus Gies
he...@licenser.net





signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] Installing OmniOS

[Heinz Nikolaus Gies]

Hi,
I've been trying (and finally succeeded after about 4 days) in installing 
OmniOS and wanted to give a little feedback. Since it was a very frustrating 
experience let me start with saying that, despite that I really enjoy OmniOS 
now that it is on the system ;) and that your guys work on the system is hugely 
appriciated. But I think that the install process can be improved, a lot.

From what I understand there are basically two ways to go, kayak, and the 
installer both have their problems, lets start with kayak sice I don't have 
much to say to that it's the path I did not choose.

Kayak might work well to add additional systems to a existing OmniOS 
installation but when starting off w/o a existing OmniOS system poses some 
problems, mostly the 'install wit hkayak from a non OmniOS OS' tels you to 
install OmniOS to copy the required files. So as a suggestion of improvment: 
package the required files somewhere easiely downlaodable and put a link in the 
manual. (If that link had existed I propably had went with kayak and you missed 
all the nice bugs I found in the isntaller ;)

The isntaller - it crashes, a lot, a lot lot. It crashes when:

- using 3TB disks
- entering partition sizes that do not fit (even so are not obviouysly wrong). 
i.e. if it tells you 110.8 GB are available you enter 110.8 -> crash (I guess 
it was something like 110.79).
- you select a disk with UEFI labels.
- randomly when cycling between parition types.
- basically any other place where you can enter data and it is not a perfectly 
valid value.

The problem with the crashing is that you need to start form scratch, and that 
can be painful.

In addition to that:

It does not allow you to select slices unless you manaually created more then 
one before hand. This can be very annoying since you need to drop out of the 
instaler to do that.

It can get into a state during slice selection where you can't change the type 
of slices any more, none could be marked as rpool

Generally unless you want a 1 full disk spanning rpool it will be a very 
painful experience requiring a lot of work in the console beforehand.

So now the 'complaining' is over on the installer and here a suggestion how to 
improve.

Since it will propably be very hard to make a good graphical installer and get 
rid of all the bugs (even so the crashes might be worth fixing) it would be 
very cool if there was a way to drop in the console, set up the disks/pools/etc 
and just tell the system: please skip the graphical thing, i created the rpool 
for you, now install the system in it and put grub onto disk 

Cheers,
Heinz


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] rsyslogd package on ms.omniti.com

[Heinz Nikolaus Gies]

Hi Eric,
thanks for the reply :). To be honest I'm not a expert on rsyslog either I just 
want to include it to ship data to papertrais so SmartOS includes the following 
default configu:

https://gist.github.com/Licenser/6282774

which looks rather sensible to me.

Cheers,
Heinz
On Aug 20, 2013, at 17:12, Eric Sproul  wrote:

> On Tue, Aug 20, 2013 at 2:59 AM, Heinz Nikolaus Gies  
> wrote:
>> Hi a little 'bug' report:
>> the rsyslogd package does not include the config file it uses as a package 
>> file:
>> 
>> /opt/omni/etc/rsyslogd.conf
>> 
>> this leads to the effect that the file gets removed when the last other 
>> package using /opt/omni/etc gets removed.
> 
> We could ship a default config file with the package, and mark it as
> editable.  That way pkg would be aware of it and would preserve local
> content.  What would be sensible default content for rsyslogd.conf? I
> don't know that product well.
> 
> Eric



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

[OmniOS-discuss] rsyslogd package on ms.omniti.com

[Heinz Nikolaus Gies]

Hi a little 'bug' report:
the rsyslogd package does not include the config file it uses as a package file:

/opt/omni/etc/rsyslogd.conf

this leads to the effect that the file gets removed when the last other package 
using /opt/omni/etc gets removed.


signature.asc
Description: Message signed with OpenPGP using GPGMail
___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss