Re: [OmniOS-discuss] Problem with upgrade from r151014 to r151022

2017-07-29 Thread qutic development 
Have you done a "pkg update" to get the latest updates from r151014 before 
switching the publisher to r151022?

- Stefan

> Am 29.07.2017 um 12:47 schrieb Даниил Ландау :
> 
> Hello!
> 
> I’m trying to upgrade my small home server with 3 lipkg zones from r151014 to 
> r151022.
> 
> I’ve moved from SunSSH to OpenSSH (in global and all lipkg zones):
> 
> # pkg list |grep ssh
> network/openssh   7.4.1-0.151014 
> i--
> network/openssh-server7.4.1-0.151014 
> i--
> 
> 
> Also I changed publisher to r151022 (in global and lipkg zones also):
> 
> # pkg publisher
> PUBLISHER   TYPE STATUS P LOCATION
> omnios  origin   online F 
> https://pkg.omniti.com/omnios/r151022/
> ms.omniti.com   origin   online F http://pkg.omniti.com/omniti-ms/
> 
> 
> But when I run "pkg update" from global zone or from a lipkg zone I get 
> errors (please see at the end of the message). It looks very strange for me. 
> Did I missed something in upgrade plan or, may be, there are some other 
> issues?
> 
> Thank you for help!
> 
> Daniil
> 
> 
> 
> Creating Plan (Running solver): |
> pkg update: No solution was found to satisfy constraints
> Plan Creation: Package solver has not found a solution to update to latest 
> available versions.
> This may indicate an overly constrained set of packages are installed.
>  
> latest incorporations:
>  
>   pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z
>   
> pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.151022:20170510T210757Z
>   
> pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151022:20170510T212740Z
>   
> pkg://omnios/incorporation/jeos/omnios-userland@11,5.11-0.151022:20170511T001737Z
>  
> The following indicates why the system cannot update to the latest version:
>  
>   No suitable version of required package 
> pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151022:20170510T212740Z
>  found:
> Reject:  
> pkg://omnios/consolidation/osnet/osnet-incorporation@0.5.11,5.11-0.151022:20170510T212740Z
> Reason:  A version for 'incorporate' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.151022:20170510T210757Z
>  found:
> Reject:  
> pkg://omnios/incorporation/jeos/illumos-gate@11,5.11-0.151022:20170510T210757Z
> Reason:  A version for 'incorporate' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z found:
> Reject:  pkg://omnios/entire@11,5.11-0.151022:20170511T002513Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/shell/zsh@5.3.1,5.11-0.151022:20170510T233501Z found:
> Reject:  pkg://omnios/shell/zsh@5.3.1,5.11-0.151022:20170510T233501Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/system/management/snmp/net-snmp@5.7.3,5.11-0.151022:20170511T003113Z
>  found:
> Reject:  
> pkg://omnios/system/management/snmp/net-snmp@5.7.3,5.11-0.151022:20170511T003113Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/security/sudo@1.8.7,5.11-0.151022:20170511T001935Z found:
> Reject:  pkg://omnios/security/sudo@1.8.7,5.11-0.151022:20170511T001935Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/library/libxslt@1.1.29,5.11-0.151022:20170511T003321Z found:
> Reject:  
> pkg://omnios/library/libxslt@1.1.29,5.11-0.151022:20170511T003321Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/compress/p7zip@16.2,5.11-0.151022:20170510T225314Z found:
> Reject:  pkg://omnios/compress/p7zip@16.2,5.11-0.151022:20170510T225314Z
> Reason:  A version for 'require' dependency on 
> pkg:/SUNWcs@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/compress/gzip@1.8,5.11-0.151022:20170510T233218Z found:
> Reject:  pkg://omnios/compress/gzip@1.8,5.11-0.151022:20170510T233218Z
> Reason:  A version for 'require' dependency on 
> pkg:/system/library@0.5.11,5.11-0.151022 cannot be found
>   No suitable version of required package 
> pkg://omnios/system/library/mozilla-nss@3.30.2,5.11-0.151022:20170510T212137Z 
> found:
> Reject:  
> pkg://omnios/system/library/mozilla-nss@3.30.2,5.11-0.151022:20170510T212137Z
>

Re: [OmniOS-discuss] Omios, hvm and AWS

2017-07-29 Thread Al Slater 
Hi Peter,

On 28/07/17 22:37, Peter Tribble wrote:
> I wish to run up a number of OmniOS instances in AWS.
> 
> The current OmniOS AMIs in AWS seem to use pv virtualization, precluding
> their use on the t2 and m4 instance types that I want to use.
> 
> 
> Worse; newer regions only support hvm. In my case, this rules out London.

That is precisely where I want to run my instances.

> So, I thought I would try to produce my own AMI with hvm virtualization.
> 
> I am looking to use omniosce r151022, is this likely to work at all?
> 
> I have read https://omnios.omniti.com/wiki.php/Ec2Ami
> , does anyone know
> how that procedure would be amended to cater for loader/hvm instead of
> pv-grub?
> 
>  
> The following should get you going:
> 
> https://www.prakashsurya.com/post/2017-02-06-creating-a-custom-amazon-ec2-ami-from-iso/

That looks very helpful, thank you for the link.

> Essentially, if you install any illumos distro you can send the disk
> image up
> to AWS and create an AMI. If you create the image by installing using Xen
> *exactly* as described, you're done. If you're getting the image from
> somewhere
> else then the phys_path to the disk embedded in the pool will be wrong
> and need
> to be rewritten, which basically means going into Xen again.

I will be using xen so hopefully all will be good...


-- 
Al Slater

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss

Re: [OmniOS-discuss] Omios, hvm and AWS

2017-07-29 Thread Al Slater 
Thank you, that clarified my understanding.

Al

On 27/07/17 22:47, PÁSZTOR György wrote:
> Hi,
> 
> "Al Slater"  írta 2017-07-27 12:17-kor:
>> So, I thought I would try to produce my own AMI with hvm virtualization.
>>
>> I am looking to use omniosce r151022, is this likely to work at all?
> 
> I haven't tryed to upgrade my r151022 with the ce updates, but I'm pretty
> sure that it must work.
> 
>> I have read https://omnios.omniti.com/wiki.php/Ec2Ami, does anyone know
>> how that procedure would be amended to cater for loader/hvm instead of
>> pv-grub?
> 
> If you use hvm, then there is no need for an extra loader. Just install
> omnios, as you would onto the "virtual" hdd.
> However, I never tried amazon's env. I experimenting with omnios on my home
> nas. (See my mail two days ago)
> 
> The only drawback what I found: if the xen hypervisor is >=4.6 (or >4.5.1 I
> don't know yet), then the pv network driver won't work.
> 
> Cheers,
> Gyu
> 



-- 
Al Slater

Technical Director
SCL

Phone : +44 (0)1273 07
Fax   : +44 (0)1273 01
email : al.sla...@scluk.com

Stanton Consultancy Ltd

Park Gate, 161 Preston Road, Brighton, East Sussex, BN1 6AU

___
OmniOS-discuss mailing list
OmniOS-discuss@lists.omniti.com
http://lists.omniti.com/mailman/listinfo/omnios-discuss