Is that in the ‘rel’ release or the ‘dev’ release?  Still no luck with ‘rel’ 
(again, on unsupported untested SmartOS build)

[root@hv1 /opt]# curl -O 
http://release.project-fifo.net/gz/${VERSION}/chunter-latest.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 24.8M  100 24.8M    0     0  4356k      0  0:00:05  0:00:05 --:--:-- 4825k
[root@hv1 /opt]# gunzip chunter-latest.gz 
[root@hv1 /opt]# sh chunter-latest 
This SmartOS release WAS NOT tested! Are you sure you want to go on? [yes|NO] 
yes
Okay we go on, but it might not work!
Creating new configuration from example file.
"s/^ip = 127.0.0.1:4200/ ...": 1: unescaped newline inside substitute pattern


> On Mar 6, 2016, at 2:14 PM, Heinz Nikolaus Gies <[email protected]> wrote:
> 
> Sorry about that, there was a problem in the build that should be solved now.
>> On Mar 5, 2016, at 21:22, Jon Dison <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> For what it's worth chunter doesn't seem to want to install on 
>> 20160304T005100Z.
>> I'm not saying it should, I know its a newer "untested" release, but since 
>> the question was asked I thought I'd add that.
>> 
>> [root@hv1 /opt]# sh chunter-latest 
>> This SmartOS release WAS NOT tested! Are you sure you want to go on? 
>> [yes|NO] 
>> yes
>> Okay we go on, but it might not work!
>> Creating new configuration from example file.
>> "s/^ip = 127.0.0.1:4200/ <http://127.0.0.1:4200/> ...": 1: unescaped newline 
>> inside substitute pattern
>> cp: cannot access /opt/chunter/share/chunter.xml
>> svccfg: Unable to stat file /opt/custom/smf/chunter.xml.  No such file or 
>> directory
>> 
>> 
>> On Sat, Mar 5, 2016 at 2:01 PM, Heinz Nikolaus Gies <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>>> On Mar 5, 2016, at 8:13, Dirk Steinberg <[email protected] 
>>> <mailto:[email protected]>> wrote:
>>> 
>>> I want to try out FIFO (after installing SDC and seeing how huge it is).
>>> 
>>> So I went ahead and was about to install when I read:
>>> 
>>> "The latest Platform Image that is supported is 20160204T080230Z"
>>> 
>>> I am running joyent_20160304T005100Z and do not want to downgrade my 
>>> hypervisor
>>> platform for trying out FIFO. There is also a specific commit in 
>>> 20160218T022556Z
>>> that I need. Are there known problems with recent platforms?
>> There are no known issues with knower PI’s they simply are not tested and in 
>> the past there have beens situations where interfaces changed and broke FiFo.
>>> Why would I need an old platform image?
>> The supported PI is determined by ‘what PI was recent when testing began’.
>>> What if I ignore this and install on a new PI anyway?
>> You will be promoted and told you run on a non tested PI and asked if you 
>> are sure you know what you are doing.
>>> Will there be any dire consequences?
>> I will send my ninjamonkeyrobot army after you, and if you have bad luck 
>> something after 2060204 changed and you’ll have a bad experience.
>> 
>> Basically we use supported images to improve the user experience, think of 
>> it as “recommended hardware” when you run an application. Sure you can run 
>> windows 10 on really old PC but the experience you get might not be as 
>> Microsoft designed it to be.
>>> 
>>> On a related note I noticed that the base dataset for FIFO 0.8.0 (released 
>>> today)
>>> is from 2014. There are many more recent releases from Joyent including
>>> the current LTS release 15.4.0. For my curiosity: what is the reason for 
>>> the 
>>> ancient dataset?
>> The 15.4 images introduces a new libncurses wich makes running the same 
>> build on 14.x and 15.x impossible, while new and shiny is good for us 
>> stability it is more important. We have installations that are running for 
>> over three years now and the pain of moving to a 15.x image would be serious 
>> at this point. However 0.8.0 introduces some concepts that will make this 
>> possible in the future, 0.8.1 is planned to be using a newer image as the 
>> update procedure going forward will be easier.
>>> 
>>> Cheers
>>> Dirk
>>> 
>>> 
>>> Am Samstag, 5. März 2016 02:02:42 UTC+1 schrieb Heinz N. Gies:
>>> We're happy to release Project-FiFo 0.8.0,
>>> this update comes with some big changes which will make the path onword 
>>> easyer. All data will be stored in a delegate dataset so that going forward 
>>> the procedure of updating will be as easy as redeploying a dataset, 
>>> packages will keep existing and continue to be used for patch updates. The 
>>> default backand changes from leveldb to rocksdb, reducing the overall 
>>> memory footprint.
>>> 
>>> Furthermore we introduce fifo_dns, dynamic DNS for zones and vm's in fifo. 
>>> This goes along with a lot of small improvement and fixes as usual.
>>> 
>>> Since this upgrade is more complicate, make sure to read the upgrade 
>>> documentation[1]! We will provide hands on help for support customers.
>>> 
>>> 
>>> Cheers,
>>> Heinz
>>> 
>>> [1] https://docs.project-fifo.net/v0.8.0/docs/upgrading-fifo#section-0-8-0 
>>> <https://docs.project-fifo.net/v0.8.0/docs/upgrading-fifo#section-0-8-0>
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "Project FiFo" group.
>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>> email to [email protected] 
>>> <mailto:[email protected]>.
>>> For more options, visit https://groups.google.com/d/optout 
>>> <https://groups.google.com/d/optout>.
>> 
>> 
>> 
>> 
>> 
>> 
>> http://www.listbox.com <http://www.listbox.com/>
>> 
>> 
> 
> 



-------------------------------------------
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&id_secret=25769125-7688e9fb
Powered by Listbox: http://www.listbox.com

Reply via email to