You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Manne Laukkanen (JIRA)" <ji...@apache.org> on 2015/11/07 16:51:10 UTC
[jira] [Updated] (MESOS-3844) getting started documentation has
flaws, corrections suggested (http://mesos.apache.org/gettingstarted/)
[ https://issues.apache.org/jira/browse/MESOS-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manne Laukkanen updated MESOS-3844:
-----------------------------------
Description:
Getting started documentation, while having great virtues, has room for improvement:
1) Documentation is illogical and wrong for this part:
" $ wget http://www.apache.org/dist/mesos/0.25.0/mesos-0.25.0.tar.gz
$ tar -zxf mesos-0.25.0.tar.gz" ...then, later:
" # Install a few utility tools
$ sudo yum install -y tar wget
..obviously using tar and wget is not possible before installing them.
2) Although vi is fine for many, utility tools having:
sudo yum install -y tar wget nano
might make editing e.g. the WANDISCO -repo file way easier for newbies.
3) Advice to launch Mesos with localhost option ( " ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos " ) will lead into a state where Mesos UI can not be reached in port :5050 in a production environment e.g. in AWS EC2. Mentioning this would help, not hinder deployment.
was:
Getting started documentation, while having great virtues, has room for improvement:
1) Documentation is illogical and wrong for this part:
" $ wget http://www.apache.org/dist/mesos/0.25.0/mesos-0.25.0.tar.gz
$ tar -zxf mesos-0.25.0.tar.gz" ...then, later:
" # Install a few utility tools
$ sudo yum install -y tar wget
..obviously using tar and wget is not possible before installing them.
2) Although vi is fine for many, utility tools having:
sudo yum install -y tar wget nano
might make editing the WANDISCO -repo file way easier for newbies.
3) Advice to launch Mesos with localhost option ( " ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos " ) will lead into a state where Mesos UI can not be reached in port :5050 in a production environment in AWS EC2
> getting started documentation has flaws, corrections suggested (http://mesos.apache.org/gettingstarted/)
> --------------------------------------------------------------------------------------------------------
>
> Key: MESOS-3844
> URL: https://issues.apache.org/jira/browse/MESOS-3844
> Project: Mesos
> Issue Type: Documentation
> Components: documentation, ec2, project website, test
> Affects Versions: 0.25.0
> Environment: CentOS 7 AWS Linux image: AWS EC2 MarketPlace CentOS 7 (x86_64) with Updates HVM (a t2.medium instance)
> Reporter: Manne Laukkanen
> Priority: Trivial
> Labels: build, documentation
> Original Estimate: 0.5h
> Remaining Estimate: 0.5h
>
> Getting started documentation, while having great virtues, has room for improvement:
> 1) Documentation is illogical and wrong for this part:
> " $ wget http://www.apache.org/dist/mesos/0.25.0/mesos-0.25.0.tar.gz
> $ tar -zxf mesos-0.25.0.tar.gz" ...then, later:
> " # Install a few utility tools
> $ sudo yum install -y tar wget
> ..obviously using tar and wget is not possible before installing them.
> 2) Although vi is fine for many, utility tools having:
> sudo yum install -y tar wget nano
> might make editing e.g. the WANDISCO -repo file way easier for newbies.
> 3) Advice to launch Mesos with localhost option ( " ./bin/mesos-master.sh --ip=127.0.0.1 --work_dir=/var/lib/mesos " ) will lead into a state where Mesos UI can not be reached in port :5050 in a production environment e.g. in AWS EC2. Mentioning this would help, not hinder deployment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)