@dafyre said in Linux: YUM Package Management:

@scottalanmiller said in Linux: YUM Package Management:

@NerdyDad said in Linux: YUM Package Management:

As of CentOS 7, DNF isn't even an option. Yum is the only thing to use.
0_1493674214761_dnf.PNG

Correct. But it has been in fedora for a while now.

Is dnf the default in Fedora now?

Yes

@scottalanmiller Thanks for this post and answering all my questions. @travisdh1 Thanks for answering all my questions as well. Good Thread!

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

@scottalanmiller said:

@Dashrender said:

Scott, you mentioned that this is all at the kernel level - could you roll your own version of this?

Sure, you'd have to write your own storage layer, though. So it's not trivial in any way.

OH.. that's where I was confused I guess... I thought the storage layer was part of KVM (that's the hypervisor they use, right?)

Not part of KVM itself. The Scale HC3 is unique, there is no software version available on the market.

So they wrote the storage layer? Cool - good to know/understand that.

Yes, Scale is primarily a storage vendor. Before they made their Hyperconverged product, they made scale out storage only. That was before KVM was mature enough to make the HC3 product. They no longer sell the storage layer, it is now developed purely and designed solely around the needs of the HC3 product so is completely unique to that. It's the storage layer and the storage integration (and support) that are their selling points. That's what makes them special and unique. KVM and the hardware on its own you could do yourself and you could easily make due with a different interface.

@wrx7m said:

I restarted the SSH service but I don't know if it was necessary.
sudo service ssh restart

It is.

@scottalanmiller

@scottalanmiller said:

We need some latency numbers from around the world. Anyone want to collect some for us?

Here is the first IP address. A long running ping (hundreds or thousands of pings) would be good, we need the final stats from that:

104.236.119.59 108.61.151.173 172.99.75.133

We have a good idea on bandwidth, IO, CPU and memory. Network latency is pretty huge.

1,200,000 packets later...
via rackspace 8 GB General Purpose v1 based in london

--- 162.242.243.171 ping statistics --- 400510 packets transmitted, 400499 received, 0% packet loss, time 400849652ms rtt min/avg/max/mdev = 79.018/79.634/184.775/2.778 ms --- 104.236.119.59 ping statistics --- 400759 packets transmitted, 400732 received, 0% packet loss, time 401132556ms rtt min/avg/max/mdev = 73.663/74.533/191.571/2.203 ms --- 108.61.151.173 ping statistics --- 400765 packets transmitted, 400749 received, 0% packet loss, time 401117767ms rtt min/avg/max/mdev = 69.861/75.792/205.164/3.167 ms

I am currently working on the storage planning for Veeam and found this site http://rps.dewin.me/

The boost to copy operations for NFS is pretty nifty.

@dafyre said:

@JaredBusch said:

@dafyre said:

As a matter of correctness... Do you have EPEL /REMI or any other repos installed in your CentOS 7 image?

The script is connecting the Gitlab RPM, that is all. The base image he uses for all of these is CentOS 7 minimal, release 1511 unless he has changed the base template on his scale cluster.

Right. I'm just curious if he has added the epel-release or any other repos to it.

Definitely no EPEL. I often use it, but avoid it in the base image.

If you want to enable PHP 7 you need to edit a different repo file to find the remi-php70 repo to enable.

nano /etc/yum.repos.d/remi-php70.repo

Wow, actually a pretty easy one but don't ask me how I guessed at this.... openSuse by default is "missing" curl, so you need to do this before you can do rpm imports:

zypper install curl

@antonit said:

@dafyre Yeah, it was pretty intense. It really digs deep to see if you have the knowledge needed. I just did a test on my own accord and was given the following:

Apache Self Assess

101: Baseline Implementation
Installation and Global Configuration

Install the Apache HTTPD Webserver via the distro's packaging system (yum/apt) Ensure that the following modules are installed and enabled: Mod Rewrite Mod SSL Configure the server admin email address (globally) [email protected] Configure the server so that its signature is displayed on server-generated pages (such as 500 Internal Server Error), and that it also includes the server admin's email address in the signature. Enable the server status page at http://localhost/server-statusaccessible only by the host 127.0.0.1
Users, Groups, and Files Create the system group webadmin Create the system user don.draper with the following credentials: Password: IXnMe2Fp Home Directory: /home/don.draper Primary Group: don.draper Secondary Group: webadmin Create the system user peggy.olson: Password: 3Hx1M8aS Home Directory: /home/peggy.olson Primary Group: peggy.olson Secondary Group: webadmin Create the directory /var/www/vhosts, with the following ownership and permissions: User Ownership / Permissions: root / Read, Write, and Execute Group Ownership / Permissions: webadmin / Read, Write, and Execute. Other Permissions: Everyone should have Read, and Execute permissions. All future files and directories created in the /var/www/vhosts directory should automatically inherit the same group ownership of webadmin.
Virtual Hosts
Configure the web server for the following virtual hosts, and specifications.
VirtualHost 1 Server Name: site1.104.239.228.184.xip.io Document Root: /var/www/vhosts/site1/htdocs Access Log: /var/www/vhosts/site1/logs/access.log Error Log: /var/www/vhosts/site1/logs/error.log Copy the content of this virtual host from /root/files/site1 to the document root
Ensure that the proper content is returned when this site is accessed athttp://site1.104.239.228.184.xip.io, and there are no errors in the logs.
VirtualHost 2 Server Name: site2.104.239.228.184.xip.io The virtual host should also respond to the following aliases: www.site2.104.239.228.184.xip.io web.site2.104.239.228.184.xip.io Document Root: /var/www/vhosts/site2/htdocs Access Log: /var/www/vhosts/site2/logs/access.log Error Log: /var/www/vhosts/site2/logs/error.log Copy the content of this virtual host from /root/files/site2 to the document root Configure Apache with any necessary PHP modules required for the site
Ensure that the proper content is returned when this site is accessed athttp://site2.104.239.228.184.xip.io, that the aliases for www and webreturn the proper content, and there are no errors in the logs.
VirtualHost 3 Document Root: /var/www/vhosts/site3/htdocs Access Log: /var/www/vhosts/site3/logs/access.log for HTTP and/var/www/vhosts/site3/logs/ssl_access.log for HTTPS Error Log: /var/www/vhosts/site3/logs/error.log for HTTP and/var/www/vhosts/site3/logs/ssl_error.log for HTTPS Copy the content of this virtual host from /root/files/site3 to the document root Restrict access to this site with HTTP Basic Auth, with the user namewebadmin and password 4v2JaLuQ Configure the document root so that a directory listing is displayed in the browser, rather than an index page. Configure this site to respond on both HTTP, and HTTPS standard ports, however all traffic that comes through over HTTP must be redirected to the HTTPS virtual host. Any self-signed certificate will do.
Ensure that the proper content is returned when this site is accessed athttps://site3.104.239.228.184.xip.io and that the traffic is redirected when accessing http://site3.104.239.228.184.xip.io. No content should be returned without proper authentication as mentioned above, and there are no errors in the logs.

Was given 3 hours to finish, and unfortunately I did not. Looks like I have some studying to do 😛

Yeah, that sounds like the site I was on. It's cool, because you can use any tool at your disposal to help you get things done. Google is your friend, lol.

I don't know why others don't follow with this. I'm sure there are reasons I can't see, but it just seems easier with a rolling release like Arch or Tumbleweed.

They can still snapshot at a point in time to create the LTS release. Maybe it's more work on their part since with a rolling release there can be so many packages that change rather quickly?

I know it's almost enough of a pain to do the upgrade from release to release sometimes to make me consider just wiping and starting over (I usually do that with my laptop and Fedora since home is on a separate drive).

@wirestyle22 said:

@coliver said:

@wirestyle22 said:

I have to look up SSL certification on CentOS 7 now. I've only ever done it on our Barracuda SSL VPN which was just an upload. Here we go

I think you need to look up SSL for Apache if you are trying to encrypt ownCloud. I think someone has a guide on here somewhere about it.

I think @JaredBusch has it in his 8.2 guide. I think he did self signed though. I'm unsure of how to do this on linux with digicert or something similar

It was a self signed for the example. but I use letsencrypt myself. Some clients using ownCloud have StartSSL certs.

I just used this myself to make a new block device in a single line. Awesome 🙂

@Rob-Dunn said:

Looks cool - I'll have to try this out. For all the flashiness of the site (I'm guessing non-English speakers), you'd think there would a little more attention given to the grammar...some of the wording on the main page is...off.

Chinese site.